I'm in Kubuntu 22.04 and I have used this relative new (at least to me) feature of "offline updates" which basically forces you to restart in order to apply the update the way Fedora and infamously MSWindows do.
I have always hated the MSWindows aggressive behavior on this but had sympathy for Fedora's way, oriented towards more stability, so I have welcomed this in K/ubuntu.
What I want to know is related to a few interconnected points:
- After enabling this I am forced to restart very often. I'm on a laptop and restarting twice a week or more is ridiculous these days. For example this required restart:
On the other hand, seeing my wifi stop during an update because wifi drivers etc are reinstalled always seemed ugly. -- Shouldn't restarts be reserved for delicate cases?
What are the delicate cases (beside kernel)? - Unattended or automatic upgrades are disabled on my system, I only upgrade if I want, but I tend to think I should update more often than I'd like to restart.
Is there a need to reboot for snap (also flatpak) updates?
Thinking about it, I would guess that all updates that involve parts of the running system excepting maybe icons and such should require restart. How come for years I have used Linux and Ubuntu without this feature?
Why is this feature optional?
I'm strongly inclined to disable offline updates OR to update less often (once two weeks?) - What "should" I do?
What happens if I don't restart after an update when I'm prompted to? (*if i simply quit the Discover notifier for example or let it run) - Will new updates be presented to me or will I have to restart for new updates?
4: no. That means that for snap, just like for icons updates, we are not prompted to reboot, but that, when we are prompted, not doing it involves a risk. I think my points are related and that opinion-orriented ones can be answered based on the non-opinion ones. But: 6 isWhy is this feature optional?. That is not asking for opinion (it's about the necessity of reboot).