I noticed that if you have updates and elected to install but not reboot you can’t go into Discover again. No message informing the user of anything. If some updates are needed via the taskbar icon showing you can go into Discover. But if you right click and say update via the update icon then again no Discover. I don’t understand why the 2 update ways. One I know is daily at some pre-determined time or something but via Discover it checks every time you load it, why and also you can’t use it while it’s checking. I find this process to be a little convoluted. For the new user they wont have a clue as to what’s goinf on and why. Just my 2 cents is all.
From what I understand, this behavior is because of the way KDE communicates with packagekit which is how it handles the update transactions on Fedora. It’s not necessarilly Fedora doing anything incorrectly, but I would guess the reason you can’t open Discover anymore is because packagekit is telling your system it requires a reboot and Discover doesn’t have any way to communicate to the user directly that in order to “reload” a reboot is required, or that there may be some other background transactions still going on. You can verify this by running the command systemctl status packagekit and seeing what the output says. I think Discover does notify users when a reboot is needed for an offline transaction, but I don’t actually have that much experience with KDE, GNOME Software suffers from similar issues and they should adress this too.
I would recommend bringing this up with KDE about updating Discover to notify the user when packagekit is handling a background transaction or reccomends rebooting the system to make it more transparent to (you) the user. It’s a valid criticism, but ultimately requires KDE to implement changes on their end.
1 Like