If I understood correctly, rpm-ostree status has a notification CRITICAL when an important update was done.
rpm-ostree status
CRITICAL
Even when updates are done in the background, fully, (which is the only way I think it should be done, leaving Discover for Flatpaks), you dont see these.
Would be great to have a GUI notification, using kdialog or notify-send.
But before doing something like this I want to ask: are Discover-independend, minimal GUI integrations of the setup or rpm-ostree wanted?
I would imagine a GUI notification listing the number of packages updated, and here this one, using kdialog, allowing to reboot instantly, when there is a critical update.
But maybe this is not what you want design-wise. I would prefer this a lot, Kdialog settable timer for automatic updates, polkit usage, notifications about background updates,...
I certainly see the value in an automatically updating OS for end users.
As far as notifications, etc. I think a system tray icon would be best. A simple icon view-refresh for restart required and make it red if there's a security update pending. If they click it, it could just do a notify-send indicating that a restart is required to apply updates. If there's a security update, it should encourage the user to reboot as soon as possible.
view-refresh
This is a feature request for Discover. Please file it upstream.
Metadata Update from @siosm: - Issue close_status updated to: Deferred to upstream - Issue status updated to: Closed (was: Open)
hmm, no its not.
rpm-ostree works perfectly. In my eyes it should be used to update a currently done system. Maybe you layered packages, maybe not, but rpm-ostree just updates your entire system. Its not interactive, you can't block singular updates and you also dont want to.
Discover on the other hand is for interactively finding software, downloading it and doing interactive singular updates.
I dont think rpm-ostree benefits in any way from being used through packagekit only. Its great that it works, but its not necessary. It confuses people, as installing an RPM will not simply work how they expect it, but requires a reboot. Also the update check slows down Discover quite a lot.
So this FR is more a question, if a GUI-driven but Discover-independend way of simply notifying about updates, would be anything to consider.
I think yes. Updates should be done automatically without ever annoying the user. But if a critical update comes, maybe you want to notify that the user should reboot NOW.
Also, notifying about a running update may be nice, as they are slowing down the system "randomly" currently.
Metadata Update from @boredsquirrel: - Issue status updated to: Open (was: Closed)
I dont think this is the right medium for Discussion, I will open a Discourse thread about this:
https://discussion.fedoraproject.org/t/92121
We are using Plasma Discover as our UI for system upgrades.
Kinoite / rpm-ostree does not use PackageKit. Plasma Discover is the GUI for applications and system updates on KInoite.
Auto-updates is tracked in https://pagure.io/fedora-kde/SIG/issue/342 and once an update is installed, a notification should pop up to ask the user to reboot.
We could make it pop up as soon as possible if there are security updates, but again, that would be a feature request for Discover to file upstream.
thanks for the clarification!