The end of Windows 10 support in October 2025 presents a great opportunity for the Linux community to collectively help users transition their still-function...
They’re fine for a stable release I think. Nvidia is on 550 for example. For Major updates, ping me next year since I’ll try it then, when new Leap arrived.
I don’t understand, sorry. what I meant is the way you as the user do upgrades. you grab a terminal, elevate and run the system update command (zypper refresh, zypper update). major version upgrades are more complicated.
I can do this sure. But this is not noob friendly the slightest. and the YaST graphical tools don’t make it much better either.
I won’t say that the update system of windows is good because why the fuck does searching for updates minutes, and other reasons. but the UI of it is much better. it tells you what will it update, it has a button for starting the process, an automatism for it too. there’s also a menu for the update history.
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.
Could be. What blows my mind is that both my PC and laptop work on Fedora, PopOS, Endeavour, and Bazzite out of the box, but network is fully broken, LAN and WiFi.
They work on any other distro I’ve tried. OpenSUSE is the only one that never gets an address. Static or DHCP, doesn’t make a difference. I’ll try again with your suggestion from a USB drive, since I don’t remember all the things I tried that did nothing to help. Thanks.
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.
When there is an update a notification pops up, you go to system tray, click on the icon and do the updates.
you mean the menu that will make your system unstable if you dont reboot immediately after updates?
if I can remember, it also does not do it automatically, by which I mean there is no setting to make it automatic.
to try to make it better I had to install a separate package, of which I have not found any information on suse documentation, to have the KDE built-in automatic update system.
and it does not work.
it restarts the system twice, after which zypper still says that all the updates need to be installed.
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.
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.
I don’t think it’s systemd’s fault that I repeatedly experienced general system unstability after installing updates with zypper.
By this I mean several elements of the system becoming unresponsive, like the shutdown, reboot, log out buttons stopping from working (them being pressed only resulting in a syslog error about being unable to start the program that shows the countdown), but also other programs like firefox acting weiry.
I don’t think it’s the fault of opensuse specifically.
And if you think about it, it’s logical that this would happen.
Because version A of programs is what is still running, but the filesystem now has version B of a lot of things including executables and libraries, with lots of changes, and the assumptions for which version A programs were coded do not hold up anymore. And they crash, not even start, or do bad things. Processes that make use of D-Bus are especially sensisensitive to this, but others like firefox sometimes get tangled into it when they load a library only after the files were updated (yes I’ve experienced that too, both on linux and windows).
It’s no wonder windows installers always ask you to close all (related) programs before installing or updating. It’s not unique to windows: android kills the app when it is updated, abd system updates require a restart as well. I don’t know what does flatpak do, but I’m sure that after updating the package, only after restarting its app will the changes get applied.
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.
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.
that’s right, but as I remember the error was talking about being unable to launch that KDE-specufic countdown overlay. journalctl has shown such an error for every time I tried to stop the session in any of the ways.
Normally updates don’t change a thing on Linux since the system runs on RAM.
that’s not how I understand the system is working. could you elaborate?
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.
They’re fine for a stable release I think. Nvidia is on 550 for example. For Major updates, ping me next year since I’ll try it then, when new Leap arrived.
I don’t understand, sorry. what I meant is the way you as the user do upgrades. you grab a terminal, elevate and run the system update command (zypper refresh, zypper update). major version upgrades are more complicated.
I can do this sure. But this is not noob friendly the slightest. and the YaST graphical tools don’t make it much better either.
I won’t say that the update system of windows is good because why the fuck does searching for updates minutes, and other reasons. but the UI of it is much better. it tells you what will it update, it has a button for starting the process, an automatism for it too. there’s also a menu for the update history.
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.
Could that be my issue? I’ve always done Gnome. WiFi is always broken. Network in general really.
To be fair, that sounds like a driver issue rather than a desktop environment. But you can try though.
Could be. What blows my mind is that both my PC and laptop work on Fedora, PopOS, Endeavour, and Bazzite out of the box, but network is fully broken, LAN and WiFi.
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 rfkilland see what’s the output?They work on any other distro I’ve tried. OpenSUSE is the only one that never gets an address. Static or DHCP, doesn’t make a difference. I’ll try again with your suggestion from a USB drive, since I don’t remember all the things I tried that did nothing to help. Thanks.
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 withsudo systemctl start NetworkManager, then chekc your connection again.leap 15.4, with KDE.
you mean the menu that will make your system unstable if you dont reboot immediately after updates?
if I can remember, it also does not do it automatically, by which I mean there is no setting to make it automatic.
to try to make it better I had to install a separate package, of which I have not found any information on suse documentation, to have the KDE built-in automatic update system.
and it does not work.
it restarts the system twice, after which zypper still says that all the updates need to be installed.
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.
I don’t think it’s systemd’s fault that I repeatedly experienced general system unstability after installing updates with zypper.
By this I mean several elements of the system becoming unresponsive, like the shutdown, reboot, log out buttons stopping from working (them being pressed only resulting in a syslog error about being unable to start the program that shows the countdown), but also other programs like firefox acting weiry.
I don’t think it’s the fault of opensuse specifically.
And if you think about it, it’s logical that this would happen.
Because version A of programs is what is still running, but the filesystem now has version B of a lot of things including executables and libraries, with lots of changes, and the assumptions for which version A programs were coded do not hold up anymore. And they crash, not even start, or do bad things. Processes that make use of D-Bus are especially sensisensitive to this, but others like firefox sometimes get tangled into it when they load a library only after the files were updated (yes I’ve experienced that too, both on linux and windows).
It’s no wonder windows installers always ask you to close all (related) programs before installing or updating. It’s not unique to windows: android kills the app when it is updated, abd system updates require a restart as well. I don’t know what does flatpak do, but I’m sure that after updating the package, only after restarting its app will the changes get applied.
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.
that’s right, but as I remember the error was talking about being unable to launch that KDE-specufic countdown overlay. journalctl has shown such an error for every time I tried to stop the session in any of the ways.
that’s not how I understand the system is working. could you elaborate?
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.