almost daily System Updates that require a reboot are getting tiresome

[skyfishgoo]

nearly every day Discover says there are updates available and often the only update is a System Update that requires a reboot after install.

if i set my system to only check for updates once a week, am i going to have to reboot my PC 8 times on the weekends?

there has to be a better way... i thought the beauty of linux was that updates can be done to the system without requiring a reboot.

[claydoh]

Generally kernel and similar security updates are the main thing that needs a reboot. Maybe certain drivers?
You can of course ignore the reboot request.

My 24.04 seldom needs one, so could it be your particular set of external PPAs or other repos?

If you update once a week, the most you'd need to reboot for updates would be...... once a week at most.

[skyfishgoo]

i don't have any other sources since i've not added any via the methods we've discussed before about where to add sources... this is a reinstall of 24.04 but i'm getting almost daily reboot requests and i did not get that from 22.04 even when i had backports turned on.

these daily requests are coming in via discover and sometimes there is ONLY the system update item

i don't even have any of the firmware updates checked...only flatpak (and of course snap which is greyed out) when i look in discover > settings

when i look in synaptic > repositories it shows as blank and when i look in Driver Manager > other software it only shows the one automatic item checked.

so what's different between yours an mine?

[oshunluvr]

Synaptic is not a KDE application, Discover is. Point being you're generally on your own when you go "off the reservation."

You can set Discover to not "force" a reboot for every update. IMO over the last several years, and maybe because the user base has expanded and maybe the devs are getting tired of every misstep by a new Linux user being reported as a bug, KDE has moved toward a more "preventative" approach for default behavior.

Just go to System Settings > Software Update and check "Immediately" instead of "After rebooting"

[claydoh]

Hmm....I keep forgetting. You probably need to turn off the "offline updates" option, found in System Settings. More info HERE and HERE.and HERE
This has been a thing since Plasma 5.22, though not sure if 22.04 or 24.04 has this on by default. I don't think it is. The "system updates" makes me think this has been turned on?

Offline updates enabled in a fairly recently installed 24.04 VM since my actual Noble drive went kaput while I was away:


These System Upgrade packages are only installed during a reboot. And System Upgrades here means anything using native packaging, unfortunately.

The nag, I dunno. Make sure both Discover and (K)Ubuntu's Apt setup are set to check for updates weekly - Via System Settings for the former, and Software Sources for the latter. I think this will take care of the premature nags -- it is easy to not notice that Discover and the native packaging system's defualt options do not share update checking schedules, so it is my guess that Ubuntu's native Apt update checks are triggering the notification.

[skyfishgoo]

i think this is it and it must have been off in 22.04 (or maybe i turned it off, don't remember) so i'm going to turn it off now and see how my update experience goes.

the daily updates, i don't mind... it just constant rebooting that driving me nuts.... i mean i've tired ignoring it for a day or two and when i did reboot it had another mandatory reboot as soon as it came back.

they were stacking up like jets at LAX.

the bit about bug reports that were solely due to not rebooting the machine is kind of funny tho... who does that?

when things go wonky, the first thing i always try is rebooting.

anyway, thanks for the help.

[claydoh]

the bit about bug reports that were solely due to not rebooting the machine is kind of funny tho... who does that?

A LOT, actually. Distro package systems don't seem to prompt for logouts, but only for significant updates such as kernels, and folks are about as annoyed and complainy about valid reboot prompts as they are about that few extra seconds of boot time.

offline updates are a bit of a hammer, as all native packaging done on a reboot, even application software. This is probably because they all can't agree on a standard method to mark packages that don't need this sort of thing, and the offline-updates is a cross platform Freedesktop thing.

I was using this on my laptop for a while, since it seemed appropriate when I was moving around and working.

[skyfishgoo]

well updates came across my desk this morning and there was no "system update" requiring a reboot, but the was a library to two.... so unchecking the offline updates box was the fix -- THANKS!

now my understanding is that while the code on disk has been updated, the code i'm currently running in ram has not... so if i want those new libraries to take effect, i'm going to need to reboot.

and that's fine with me as i'm not having any issues with whatever libraries are currently in use and will likely reboot again before too many days go by as there always seems to be some reason to do so.

[oshunluvr]

Generally, I reboot when I'm taking a break. Probably more often than really necessary, but I have had small issues magically disappear after a reboot. I totally get not want to see that constant nag tho...