when you have “offline updates” selected, you will be prompted to restart after EVERY update that requires your password to install (i don’t recall flatpak updates triggering the restart).
it gets to be a bit much restarting every day almost, so i have it turned off.
today however a 2nd wave of updates came down for mesa and freedesktop so i rebooted just to make sure those are active….
there was no prompt or anything to indicate that i should do that
Unlikely to be system components but applications.
Restarting them individually would be enough to get the new version.
The bot sounds like Flatpak Runtimes, so any application using them would get the most current version in its next (re-)start.
I guess that would be a bit much but I guess each taskbar entry could indicate (this program had and update)
oh, so for mesa and freedesktop ( or other library files) the new version will be loaded in to memory by whatever application i launch that needs it?
so i wouldn’t need to re-launch the entire plasma desktop to get those kinds updates to kick in?
for already open applications, i agree it would be a bit much to have each of them flashing to indicate one of it’s dependencies has been updated.
for this i think just a simple color change of the restart icon or even the discover icon in the system tray would be a reminder that perhaps not all the open applications are running on the latest update you just applied.
Stuff like that would be more than advanced for a simple user. Some people just need to know that after their restart they will boot in a new version. Nothing more. Hence the minimal implementation of the feature. I use an Atomic Desktop(bazzite) and in that Distro all system updates are always offline for stability and use simplicity. Yes its awesome that linux has the ability to not restart on updates and do them on a live system but when you want bulletproof stability its just not worth it.
Yes a simple color change would be enought or at least more than a start and much better than someone making his own solution for his distro.
When it comes to a DE integration is always better for the experience.
Like I said, if you’re using Discover, it already tells you you should reboot after performing a system upgrade. If you’re not using Discover, all bets are off. If your distro doesn’t ship Discover, it’s kind of their own issue, right?
Hence the request of disconnecting the whole update process from discover so Plasma can be used without Discover for systems that want to only use flatpaks and dont want something that includes PackageKit.
Plasma needs a way to notify a user about updates that is fully integrated in its UX and the way its right now its tightly integrated IN Discover. I dont see why “all bets are off“ is a good idea in this regard.
I appreciate your time to answer and provide feedback. If someone on the KDE dev team finds this int resting I bet they will pick it up as I dont have the needed skills to develop/recommend a solution on the matter.
I am pretty sure Discover can be used without the PackageKit backend.
It is the main software management frontend of KDE Linux and that does not have traditional packages either.
Making an educated guess about our current setup, I think the process that “knows” this status is DiscoverNotifier and it displays that status as an icon (in various states) in the system tray area.
Assuming this is true, we could additionally expose this status as one or more D-Bus properties.
This could then be used for two things:
That sounds more than amazing.
If you end up wiping up a feature I would love to help you try it. I appreciate your response