This is my one main complaint about Fedora Linux.
@heartsofwar @UntouchedWagons
I use Discover on Debian testing and Arch, never once did it force me to restart on Arch, but on Debian it would say it is recommended.
I don’t think that’s forcing me to restart, so I guess Fedora does that differently. 🤔
AFAIK no distro forces you to reboot, but they all require it for some updates to take effect. You can’t reload the kernel while the system is running.
Fedora just makes that clearer to the user by only installing those updates when they’re going to be active - after a reboot. I think it also blocks new system updates until the current set is completely finished.
You can disable offline updates in the system settings, but I think they’re a good idea, especially for the average user.
If the kernel, initramfs, or a driver is updated, you have to reboot the computer to apply them (you can’t reload the kernel while it’s running). A user might not know or notice this, so GUI installers (and some CLI tools like pacman on Endeavour) often warn the user or sometimes force a reboot.
I thought we would have learned from Windows, you should never force a reboot.
I’ve never seen a distro force a reboot, Windows style. Only ever advise people to reboot.
Well, then I don’t understand the downvotes, lol. The person i replied to said sometimes a distro will force a reboot, I said that’s bad, and a bunch of people apparently disagree with that.
pkcon refresh
Discover checks knewstuff (global themes, plasmoids, etc.), Flatpaks, firmware and snaps, (which all have a relevant backend package something like (discover-backend-packagekit). Discover, well more like PackageKit, will let you know if a reboot is necessary if there’s something like a kernel update.
You can turn it off in the settings (may be system settings, think it’s called offline updates).
It’s a feature Gnome added and then KDE added too. Fedora isn’t the only distro to implement it, but the most popular.