Discover bugs the heck out of me. Too much "Windows" attitude - mostly a rant...

[oshunluvr]

I rarely use Discover. I'm an old-school "apt" guy. Once in awhile I open it because it will update a couple things apt on the CLI won't - some themes, mesa, etc.

Sometimes I'll let it do a full update, which often results in a "reboot to complete update" message or something like that. Then it puts you through the laborious "reboot-install stuff-reboot" cycle which is totally annoying and absolutely not necessary. It's almost like Microsoft developed Discover.

Now, I've been using Linux since 1996ish. I know damn well very little requires a reboot to take affect after updating and even less requires a reboot before installing it. For example, you have to update a driver or install the latest kernel, you have to reboot for it to take effect and be used but there no valid reason to reboot immediately and you never have to reboot just to install it in the first place - unless you use Discover.

The icing on the cake: Today when I open Discover the only thing needing updating was Brave Browser. Not a kernel, not a driver, not even a Kubuntu component. I figured it would be fine. WRONG. Discover wants me to do the double reboot to update a web browser. A WEB BROWSER!

I'm probably going to file a big report on this. It's just too stupid for words. Discover has never been very good and I don't see it getting better. Muon looked looked promising for a couple years but was then unceremoniously dropped. The sad thing is, a robust, easy to use package manager is one of the most important parts of any distro.

I understand why so many people just install Synaptic and forget Kubuntu package managers.

[Snowhog]

I liked Muon. It's too bad that no one wanted to take on that project after Jonathan stopped maintaining it. I don't use Discover for package management. I do that from the CLI. I do have Synaptic installed, and have occasionally; rarely; installed/deleted/purged using it. But the CLI is my go to.

[claydoh]

Yes, I had a small rant somewhere (reddit? KDE's bug tracker?) about the all-or-nothing aspect to the systemd offline-update setup for this exact sort of reason.
The feature isn't a Discover feature in itself, and of course can be turned off.

The good thing I can say about it is that it has imo made for much fewer bug reports and complaints from normies those who updated plasma or some system libs, but haven't logged out or rebooted or reloaded things in days, and things like the lockscreen get busted.
I want to say that this feature may have been added instead of solving that sort of problem in a more elegant way

I guess the "immutable" (bad label, btw) may be a better model, for updates at least. System updates don't get applied, or rather don't take effect until a reboot to the updated image/snapshot, so you can't as easily face a mix of old and new libraries.

But like it or not, the more normies move to Linux, the more of this sort of thing will be the.....norm in the more mainstream distros.

[oshunluvr]

Yes, I had a small rant somewhere (reddit? KDE's bug tracker?) about the all-or-nothing aspect to the systemd offline-update setup for this exact sort of reason.
The feature isn't a Discover feature in itself, and of course can be turned off.

The good thing I can say about it is that it has imo made for much fewer bug reports and complaints from normies those who updated plasma or some system libs, but haven't logged out or rebooted or reloaded things in days, and things like the lockscreen get busted.
I want to say that this feature may have been added instead of solving that sort of problem in a more elegant way

I guess the "immutable" (bad label, btw) may be a better model, for updates at least. System updates don't get applied, or rather don't take effect until a reboot to the updated image/snapshot, so you can't as easily face a mix of old and new libraries.

But like it or not, the more normies move to Linux, the more of this sort of thing will be the.....norm in the more mainstream distros.

Your explanation makes sense but doesn't lesson my crankiness about it (lol). I obviously didn't know it was a systemd function. I'm gonna find out how to turn it off or maybe fix it so it works better. I despise being treated like an idiot.

I too have feared dumbing down to a Windows level will be the new paradigm for mainstream distros. It wouldn't bother me nearly as much if it was actually functioning correctly - i.e. asking for a reboot only when it was actually required. The update for Brave-browser is a clear example. It isn't part of the distro and has ZERO dependencies when updated, so why am I rebooting twice to update it when actually ZERO reboots are required? Really, really insulting and stupid.

[oshunluvr]

Turns out you can turn off the "reboot many times" feature is System Settings but it's slightly obscure. Go to System > Software Update and change "Apply system updates:" from "After rebooting" to "Immediately". I haven't tested it yet because no updates are currently pending.

[claydoh]

Turns out you can turn off the "reboot many times" feature is System Settings but it's slightly obscure. Go to System > Software Update and change "Apply system updates:" from "After rebooting" to "Immediately". I haven't tested it yet because no updates are currently pending.

yes, that is the setting you need.

https://www.freedesktop.org/wiki/Sof...SystemUpdates/
https://www.freedesktop.org/software...e-updates.html

The only way I think to implement this is to have all the software contain (even more ) metadata labeling it as appropriate for offline updates, or something along those lines, so that Discover and Gnome Software can then install some things now, and others set for the offline process.