Need help resolving the issue? Let me know what the error is and how you're trying to fix it.
Need help resolving the issue? Let me know what the error is and how you're trying to fix it.
I understand you're noticing something after using fedora gnome without any problems.
For Wayland users, attempt to log in via "Gnome on X11" or similar.
This might have come across as a bit casual or informal. Let's keep it professional.
I discovered the ease of Arch Linux after noticing its smooth performance. It worked without any crashes or errors, most importantly eliminating the need for a USB drive to repair the damaged journal on the ext4 root partition. Apparently, Debian and its derivatives don’t have the fcsk tool in their initramfs, which is essential for fixing corrupted journals. Every time Windows updates, you usually have to rely on it. On Debian, you must use a live USB, which takes time because it involves running fsck.ext4 -yf /dev/sdX; mounting the drive and booting fine.
I'm trying Fedora 28 now after a friend suggested it. So far I haven't had to fix the journal, which is great. I'll let you know if the red family solves the problem—I'm impressed. Everything runs smoothly, unlike Windows and Arch. My idle performance is solid at 28, and with an H105, the background stays minimal, which is a big plus for me!
Yes, I was using the complete GNOME stack on Arch. Was it AWS or I3?