As per the image, kclock tells me it’ll update on its own in N days. The notification appears randomly, unrelated to opening Discover in the background. That’s unusual and I’d say useless. How do I “close” it anyway?
Why do I need to know this will happen? Do it or don’t do it, but stop telling me about it. Discover doesn’t see the app.
IOW, this notification and app update behaviour is different than everything else and to my mind not useful at all.
When a snap gets updated without writing it’s cached data from ram to disk you will lose that data, this is why you get asked to close the app, in a properly configured system this will immediately trigger the self-update of the package and within a few seconds you get a notification that the app is ready for use again…
Thanks for the explanation. How do I close it, then? I mean, the window, the app isn’t visible in the task bar, so I presume the daemon is alive headless in the background. Do I need to reboot to get there from here?
interestingly kclock doesnt have the same contact: info as all other KDE owned snaps (seems like another packaging oversight) … other KDE owned snaps all point to:
Hehe! That’s actually where I started yesterday and they sent me here. I think this is the end of me chasing my tail. Thanks for your perseverance and know-how.
