So, after EndeavourOS’s GRUB comitted suicide, me being too stupid to understand chroot despite wiki “tutorials” and the community rather trolling & gaslighting me instead of helping I decided to give Nobara a go. Usually I am a Plasma KDE guy, but thought since it’s been a long time I try it out, especially since you can have it in a more classic configuration those days again, even though I’d miss out of Wallpaper Engine.

Unfortunately my experience has been nothing but awful. A bunch of random bullet points of my experience:

  • I had real trouble connecting my BT headphones. At first it was “connected”, but not really. Tried a fresh pairing mode, but then it showed two headphones. Then it connected, but as soon as I tried to adjust the audio input / output settings it lost audio again and I had to repeat it yet again. Now it works, and I decided to never touch the audio settings ever again.
  • “Files” is constantly crashing. Using the search? Crash. Going backwards? Crash. Try to do “something”? Crash. Do nothing? Probably also crash (hyperbolic).
  • “Files” data transfer for copying & deleting files is slow as hell for whatever reason (on decent Samsung SSDs mind you).
  • “Files” cannot multitask. If you’re copying, scanning, deleting or whatever, it won’t do anything else until that process is done.
  • “Files” and other Gnome applications frequently bug out if you try too many things at once, freezing or crashing them.
  • “Files”, or even Gnome as a whole, is so incredibly scrapped for features to achieve its simplistic look, that it lacks actual functionality.
  • Gnome’s settings are also missing for everything, or hidden in a gazillion different config menus, some of which I already forgot how to access again.
  • Scaling scales not just the UI, but also 3D applications like games, reducing their actual resolution and making them blurry. The UI seemed to be blurry as well.
  • Mullvad VPN’s tray icon somehow turned into some three dots with a weird background.
  • In the tray menu there’s also a VPN toggle, which shows Mullvad, but being turned off. Turning it on disables my connection and I have to reconnect through Mullvad, which turns the toggle off again. No way to remove the redundant toggle as far as I can tell, but maybe it’s in some hidden settings menu that I have yet to find.
  • OpenRGB in this does not work with my NZXT Hue 2 Ambient. Keeps asking for resize zones, which according to a search should not be necessary, and wasn’t necessary with the one I used in EOS either. Selecting any color just turns the LEDs off.
  • Launching the Battle.net launcher through Lutris it also opens some ghost “OpenGL Renderer” application with it, taking up space on the task bar.
  • Battle.net launcher can’t be maximized without constantly resetting or displaying information beneath the task bar.
  • Can’t launch .sh files unless I explicitly right click & Run as program.
  • Unfortunately it then launches with an additional empty terminal window, yet again taking up space on the task bar.
  • Had to create a new FF profile because using my old one somehow was unusable in regards to its performance.
  • The weather location for the little clock thingy apparently can’t find anything, city or country, except some locations that aren’t near me.
  • Can’t remove my own review in the Software center for one of the apps that I did prematurely.
  • Tray area also has this little tiling menu. I tried tiling, hated it. Couldn’t find a way to remove that icon to save space on the task bar.
  • After a lot of apps started to hang I tried restarting, just to be left in a blackscreen and the PC not shutting down. Had to hard reset to restart.
  • No EurKey keyboard layout. There’s a ‘German (US)’ one that’s close but it’s missing symbols.
  • Maybe probably more things that I can’t recall right now.

And that’s just after a few hours of usage. I was making fun of the tiny issues in KDE before, but if I have to choose between that and this disaster then I’m probably going to switch to the KDE edition, if I cannot find solutions to all this. I really don’t understand how people can deal with it? Or am I somehow the only one?

You are viewing a single thread.
View all comments View context
0 points

Try opensuse tumbleweed. It is a bit like arch(rolling release and such) but has more testing and less breakage. It has pretty good KDE support, a very good configuration tool and is one of the most secure distros in its base installation. Also good for gaming imho.

permalink
report
parent
reply
1 point
*

@FaeDrifter
Tried to install it on my old laptop for testing and the installer just gives me this warning before installing:

“Boot from mbr does not work together with btrfs filesystem ang gpt disk label without bios_grub partition. To fix this issue, - create a bios_grub partition, or - use any Ext filesystem for boot partition, or - do not install stage 1 to MBR.”

I really have no idea what it wants. I used the guided partitioning so I would expect it to handle that for me? Also, why do they not have a working live environment to test it before installation? Honestly not a great start.

Edit: Oof. So I just tried to install it on my desktop, first one failed tremendously and didn’t boot. Tried again and wiping the partitions proper instead of “on demand” of the garbage installer. Got a system, try to switch down to 1080p and it gives me this super stretched pancake resolution instead. Hell no.

permalink
report
parent
reply
0 points

You booted in bios legacy mode and tried to install to a gpt formatted disk without a dedicated /boot partition would be my guess.

It’s messed up, probably a bios setting related to uefi. Aeon is still in beta and doesn’t handle edge cases that well.

As for your second issue sounds like a waylaid issue with switching resolutions, usually simply relogging fixes that.

You make it sound as if these are distribution issues, these are either weird bios settings or post install issues with a very recent compositor version. Do you think opensuse ships its own drivers or window managers?

permalink
report
parent
reply
1 point

I booted in bios legacy mode?
What “weird bios options” could an old 2009 laptop bios possibly have, that are used by default on top of that and never caused any sort of issues with any other Linux distro before? The only ones that didn’t run on that thing were both Nobara variants, which is likely more of an old gpu issue.

I’ve had many wayland issues on other distros before, but never this specific one. It’s usually the same on every one, like blurry scaling, scaling affecting games, fsync causing frequent few seconds long blackscreens, or just a lot of game specific stuff. The issue here did not fix itself even after a reboot. I really don’t care where the issue stems from, I can only say that this was very unique to OpenSUSE.

permalink
report
parent
reply

Community stats

  • 1

    Monthly active users

  • 267

    Posts

  • 1.2K

    Comments

Community moderators