I approached this as they are more techie than a regular user, so they can learn Linux faster if they want. Otherwise, it’s their job and they are not a regular user. It’s the same for MS Office too. If it’s related to someone else’s job, it’s most likely irreplaceable. However MS Office is not a must for people who just want to write or do some spreadsheet.

Basically I exclude jobs from “everyday users”.

Well, it’s true that Photoshop has no real competitor, at least in the FOSS world. Otherwise we wouldn’t have this conversation. :)

I mean, I get MS Office part but do normal people use Adobe stuff (aside from Acrobat)? As I see, normal people don’t even know how to use Photoshop. The ones who can use Adobe products can use Linux as well without a hassle in my opinion. However, a change requires to relearn things. Probably that’s the reason people don’t seek a change, unless they feel a little adventurous.

If it ain’t broke, don’t fix it! Hopefully, Microsoft will break that cycle.

I prefer that over NT or Windows.

I guess I’m gonna say Linux Mint here too, even better LMDE.

So, it acts like a hand tool from pdf readers?

systemd always requires root password for poweroff and reboot commands and polkit does that for you normally when using GUI. However that problem occurs when polkit timeout runs out. I don’t know the exact mechanism behind it so I cannot tell exactly when it happens. When it doesn’t do that, those commands don’t run via a GUI. So this is on part systemd and part the distro.

Hehe, it was fun to watch. It baffles me that Ubuntu still has those errors though.

It actually doesn’t crash, it just cannot show the requirement of the root password in a dialog. I think this can be fixed via lengthen the timeout of polkit. Though I can understand why most distros don’t change the default time because of security reasons. It would be nice if they give an option for it, at least for personal use cases. However, completely removing that timeout would be a security problem, even if the only user is you.

and the new version of all the software that is still running with the old version.

That’s why it’s recommended to reboot after a major update, and usually there is a notification for that. But there is usually no need to rush the reboot if you work on something.

If one needs a certain release of a program I guess using the AppImage version would be the best.

Oh, I meant a running system. Usually you would only need to reboot if you want to use the new kernel right away after an update. For most of the programs, you don’t even need to restart them if they’re already running. However, if you restart them they will run as the newer updated version.

Not completely but kind of, all those poweroff, reboot etc. tied to systemd, though I believe this is mostly related to polkit run out of time. Can be fixed with a longer timeout. This also happens to me on Arch and yeah it’s kinda annoying.

Normally updates don’t change a thing on Linux since the system runs on RAM. However, with these systemd updates, things have changed. Without systemd, it’s still the same more or less.

you mean the menu that will make your system unstable if you dont reboot immediately after updates?

Not sure what that is or what menu it is. But yeah, the updates are not automatic, you have to manually start it. That “must restart after the update” thing is related to systemd, not openSUSE.

If someone wants an auto update system, that can be arranged with scripts. No idea where that could be done via GUI though. Sorry, I cannot check it right away since it’s not my system. I don’t use openSUSE or KDE myself.

It’s a personal list for newbies and it’s probably a good idea to follow this list for them. However end users are a much bigger cluster, I’m an end user too. Last time I checked I didn’t have a grey beard.

It’s my workstation and I’m using it as how I’m comfortable with it. It just requires a familiarity which newbies don’t have.

Nice personal list but I almost do the opposite of everything. I only do the not using dual boot part from this list.

No problem.

Hmm, if there was a soft-block or a hard-block that would affect all the other distros as well. In that case, trying from a Live ISO would indeed help. Maybe this could be something related to Network Manager. Can you check interfaces with ip a?

Also check if Network Manager running with systemctl status NetworkManager. If it doesn’t work, start it with sudo systemctl start NetworkManager, then chekc your connection again.

Does network work on those distros but not on openSUSE, or network doesn’t work at all?

Maybe it’s a switch issue? Can you try sudo rfkill and see what’s the output?

Solved the issue but thank you for the reply. It looks like a nice GUI option.

Found my answer faster than I thought. Thanks though, this might be useful for people who use Hyprland.

To be fair, that sounds like a driver issue rather than a desktop environment. But you can try though.

Not sure when the last time you used openSUSE but the reason why I think it’s noob-friendly is you don’t need a terminal to update the system (talking about the KDE version here). When there is an update a notification pops up, you go to system tray, click on the icon and do the updates. You can even see a list what’s been updating. It doesn’t even ask a password, probably thanks to polkit.