muhyb

joined 2 years ago
[–] muhyb@programming.dev 1 points 1 year ago (4 children)

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.

[–] muhyb@programming.dev 1 points 1 year ago (6 children)

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.

[–] muhyb@programming.dev 1 points 1 year ago (8 children)

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.

[–] muhyb@programming.dev 1 points 1 year ago (10 children)

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.

[–] muhyb@programming.dev 1 points 1 year ago

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.

[–] muhyb@programming.dev 1 points 1 year ago

Don't smoke catnip, kids!

[–] muhyb@programming.dev 7 points 1 year ago (2 children)

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

[–] muhyb@programming.dev 5 points 1 year ago

Where is she? I can't see her!

[–] muhyb@programming.dev 12 points 1 year ago (3 children)

Yeah, they consume all the upvotes. :3

[–] muhyb@programming.dev 2 points 1 year ago

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.

[–] muhyb@programming.dev 2 points 1 year ago (2 children)

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?

[–] muhyb@programming.dev 3 points 1 year ago

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

view more: ‹ prev next ›