This is my one main complaint about Fedora Linux.
Those updates in Discover are for flatpak, not dnf. You can verify that with
flatpak update.As for discover wanting to restart to do their update, that’s a fedora thing for an extra level of safety while updating. You can read about it here.
As for discover wanting to restart to do their update, that’s a fedora thing for an extra level of safety while updating
That shouldn’t trigger for flatpaks though. No risk of breaking the system while updating flatpaks
deleted by creator
Because those are Flatpak packages
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.
So when people say ‘force a reboot’ there are two things it can mean:
-
a reboot is required for updates to actually take effect. Linux sometimes does this for things like the kernel.
-
the OS forces you to stop everything you are doing and reboots the machine. I have only ever seen Windows do this. Not Linux, not even MacOS.
This might be where the confusion is coming in. @rtxn is referring to number 1 but the rest of us are referring to number 2
-
I had reverse situation, discover said there’s none of apps i need or/and updates, while dnf was working flawlessly
pkcon refreshLooks like flatpaks updates
deleted by creator
I agree that packagekit is annoying and I just have automatic updates in the background using
flatpak update -yandrpm-ostree update.






