First box is irrelevant (old bug) hence the comment about the bottom one on the same post. The only notification that shows is the bottom one.
As I said the problem about update notifications and the need to restart is something that I have already talked on a long thread about. J0rge said that I should try the KDE forums regarding this feature as they have much better way to provide a tool on this matter. I actually did that and I got a really good engagement from actual KDE devs!
Also the reason of my “heat” as you said is the stark contrast in the way a moderator is communicating with a user! Here is an example of the answer I got from one mod to another. I dont just come here requesting stuff willy nilly. Anyway I agree with you that this was not my best moment. It wont happen again. If I had the minimum of knowledge to develop that I really would. For now we have the popup for the month tho.
Well, I’m gonna try to cook something up. I don’t think it’s going to be hard. On the GitHub open issue page, one thing they’re concerned about is peppering the user with too many notifications, and I can understand that.
I’m using my father in law as a test subject The goal is to remind him to reboot if he forgets.
I’m thinking I’ll have the notification appear only once when a new image is staged, so it doesn’t keep coming back every 30 minutes when triggered by the systemd timer
I really hope its not! In the meantime you can show your love to the dev that actually acknowledged a possible integrated solution to the problem over here.
A solution on the level of KDE will provide a possibility for everyone to come with the DE instead of the need to be an external script. In the meantime I bet that you can cook up something that will be more than enough for your uncle tho. Be sure to post updates on your project here I bet more people will try it and provide you with feedback.
In case you did not do the install as of fedora 43, kinoite (KDE version of fedora atomic) offers the user an update dialog to restart after a week by default. Changes/KDEKinoiteAutoUpdateByDefault - Fedora Project Wiki . ofc this is based on the discover store and not bazaar so I dont think it can be ported to ublue except if they have the notification as a separate part and not integrated on discover.
It’s pretty safe nowadays to stay without updates for a month.
Bazaar can take care of the normal updates like browsers and other apps. And if Firefox had a ESR version in Flatpak, it would’ve been even better (but it doesn’t). If something is not working, then… well… reboot the PC that will also apply a new image/update and eventually fix something.
I do agree with your point. For the most part, it’s not an issue. Where it can be an issue is if (and let’s be honest, it’s pretty low but non-zero probability) there is a zero-day vulnerability in a browser or one that is not patched right away, AND that vulnerability is used to break into the host OS due to some sort of privilege escalation bug in the OS.
I’ve been experimenting with changing the UUPD timer and this works well:
[Unit]
Description=Auto Update System Timer For Universal Blue
Wants=network-online.target
[Timer]
# Run daily at 4:00 AM
OnCalendar=*-*-* 04:00:00
# If the system was off/suspended at 4:00 AM, trigger immediately on resume/boot
Persistent=true
# Wait up to 15 minutes after triggering.
# Spreads the load on update servers (thundering herd protection).
RandomizedDelaySec=15m
[Install]
WantedBy=timers.target
This configuration guarantees at least one update attempt per day, regardless of how short the user’s sessions are. OnCalendar follows the wall clock, so if the system is asleep or powered off when the scheduled time arrives, it will run as soon as the system is active again. The issue is that OnUnitInactiveSec is paused while the system is suspended or powered off, so it can take a long time to accumulate the six hours it’s currently set to if a user is a sporadic short bursty laptop user.
You could also leave OnUnitInactiveSec as both can coexist.
FYI, “inactive” refers to the time since it was last deactivated and accumulates time up to the number that is specified.
The goal is to remind him to reboot if he forgets.
that will also apply a new image/update and eventually fix something.