Yup indeed. That’s a good idea.
Edit: although it might not be clear, when there is only a notice about an update like in the screenshot and then, after the user unlocks, sees there is nothing to take action on (not that there should be, as you want it to be as non-intrusive as possible). Might get confused as to what to do, to get rid of that lockscreen message (although personally I would at some point consider a reboot to see what happens).
Same thing I always say, engage with the projects that make the stuff. If you want graphical applications talk to GNOME or GNOME app developers who know how to make that stuff.
Got it. I will make a request both on Plasma and Gnome boards for this feature. Atomic desktops are becoming more prevalent by the day an a notification to update does not specify the need for restart to boot into the new image.
There’s a better chance of that if you don’t shut people down who are trying to contribute.
This has nothing to do with “atomic” or anything we’re doing here! This is a distribution agnostic feature.
Oh I didnt mean to shut you down or something sorry if it seemed like I meant to do that! I just thought that this is something small and so integrated that the main devs of ublue would have a much better beginning on a solution. English is not my main tongue hence something I said might sound wrong.
Got it. Just to specify I meant it as a comparison to lets say arch that doesn’t require a restart after an update(most of the time). But yeah I get exactly what you mean.
No problem. I can be overly sensitive. My apologies.
I create the feature request on the Developer forum of KDE. I am posting it here in case someone far more experienced than me wants to add information on the matter that I most likely did not fully provide.
I think the easiest way for this to be implemented would be a Plasmoid that you could have as a widget on your taskbar like that person earlier had with their gnome extension and having it turn green when you have a new deployment.
Trying to integrate bootc/rpm-ostree updates into discover/plasma is not really in scope for us.
Why not? If plasma had a flag integrated in the UI that indicates that a update is pending wouldn’t the bazzite team use it. As Jorge said this is a distro agnostic feature that everyone would benefit from.
Instead of everyone having their own solution to inform the user of the update they could use the DEs (in this case Plasma) available tool on the matter.
Right now the only reason we dont have some integrated method is because the feature is based on discover. Hence my post on the KDE forums about separating the tool and making it more of a separate QOL feature any distro can utilize while staying integrated in the Plasma UX.
I would recommend you give a read of the Post I made on the KDE forum, Actual KDE Devs had a positive reaction to the feature! (here and here)
I think that some of the pieces already exist in KDE to support this, just not for rpm-ostree and bootc yet. I would think that this would fall to the Fedora KDE sig to work on. Once it is available in the Kinoite image, Aurora will get it too. I think there are settings to turn it off too. I may be wrong but ChatGPT seems to give me that impression.