Because Plasma Discover and Gnome Software use PackageKit to talk to DNF. PackageKit will download and cache updates for them to be installed later, but if you manually update via DNF, Plasma Discover and Gnome Software won’t know and therefore they will tell you there are still updates when there isn’t and take up space in the process.
Also, Plasma Discover and Gnome Software force a restart after updates because its easier than the user assuming they don’t have to restart when sometimes they should. Just easier to force it…
Those three reasons are why I dislike PackageKit and refuse to use the respective DE software update apps.
@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.
![[Fedora 39] Why does Discover say there's updates while dnf say there's none? Also, why does Discover need to reboot to install said updates?](https://lemmy.ca/pictrs/image/266cefdc-1084-47c5-9d90-d53ce65471de.jpeg){kind=link}
TL;DR: Because Discover uses PackageKit…
Because Plasma Discover and Gnome Software use PackageKit to talk to DNF. PackageKit will download and cache updates for them to be installed later, but if you manually update via DNF, Plasma Discover and Gnome Software won’t know and therefore they will tell you there are still updates when there isn’t and take up space in the process.
Also, Plasma Discover and Gnome Software force a restart after updates because its easier than the user assuming they don’t have to restart when sometimes they should. Just easier to force it…
Those three reasons are why I dislike PackageKit and refuse to use the respective DE software update apps.
@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.
I agree that packagekit is annoying and I just have automatic updates in the background using
flatpak update -yandrpm-ostree update.