Last night I checked the update log ( journalctl -u ublue-update.service ) and noticed that the last entry is from Feb 14. Prior to that it would automatically check for updates every 6h - I know that since I used to check the logs daily.
I checked the auto update status with ujust toggle-update and it says auto updates are on.
I then ran ujust update and got ostree and flatpak updates. Prior to that my PC had been on non-stop for over 16h (which it is daily). Maybe it was a coincidence and those updates came in in the last 6h, but it seems very unlikely.
❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/aurora:stable
Digest: sha256:ee5d2e2c681c0c3a42fc2deafa937ddbbed20733073aca4c8a82322ad43afc79
Version: 41.20250224.6 (2025-02-24T16:00:28Z)
ostree-image-signed:docker://ghcr.io/ublue-os/aurora:stable
Digest: sha256:48560c2aa9fbc6a2e1a1c21fc25ec7bd164e17020826d2a41cf36f00353a4424
Version: 41.20250209.1 (2025-02-09T05:57:01Z)
~
❯ systemctl status rpm-ostreed-automatic.timer
● rpm-ostreed-automatic.timer - rpm-ostree Automatic Update Trigger
Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed-automatic.timer; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/rpm-ostreed-automatic.timer.d
└─override.conf
Active: active (waiting) since Wed 2025-02-26 10:00:53 CET; 3 days ago
Invocation: 18dce54d1f4c4e7bbe9cdc7a93b294f2
Trigger: Sun 2025-03-02 04:01:27 CET; 13h left
Triggers: ● rpm-ostreed-automatic.service
Docs: man:rpm-ostree(1)
man:rpm-ostreed.conf(5)
Feb 26 10:00:53 aurora systemd[1]: Started rpm-ostreed-automatic.timer - rpm-ostree Automatic Update Trigger.
I only reboot my pc once every 2-3 weeks, and suspend it overnight. During the day it typically runs for >14 hours.
Note that it says it hasn’t run since boot, and that next trigger is tomorrow at 4am. I have checked the output every day, and so far all triggers have been for 4am the following day when my PC is suspended. It means the update trigger will never run while the PC is on (unless I’ve misunderstood the output). If I’m mistaken then please enlighten me.
Also, where is the 4am time set/configured?
With the previous ublue update service, the update check would fail right after waking up the PC (I posted about it here), but it would then run again after 6h so it was almost moot. Is this “new” update trigger a temporary solution? Because it seems less reliable.
Seems that the timer is triggered after wake from suspend, but the rpm-ostreed.automatic.service fails due to the exec condition not met.
From the /usr/lib/systemd/system/rpm-ostreed-automatic.timer.d/override.conf
xecCondition=/bin/bash -c ‘[[ “$(busctl get-property org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager Metered | cut -c 3-)” == @(2|4) ]]’
If I run this command it checks out to 4 on my machine. So could it be that the Network Manager is not yet started when the update service is run directly after wakeup from suspend? If yes how can that be fixed?
Should we file a bug ticket about this so it can be fixed, or is it a already a known issue?
Right now we don’t have any automatic updates, which is one of the key features of Aurora/Bluefin. If the update time is tz dependent (i.e. 4am in CET but 10pm in EST) then some devs might not even be aware of this bug.
My laptop usually is just sleeping during the night time here in the EU. And I just
So looking at that, next time the timer triggers is Trigger: Mon 2025-03-10 16:43:35 EET; 15min left
As this is not my work laptop, its usually opened before work (around 6-7am) and then put to sleep and opened in the evening again. But I usually also update manually in the morning (atleast sometimes).
Although I can’t just now remember was the service checking once or twice a day for updates. But looking at the service components atleast the trigger seems to be there
Thanks. That’s weird, my trigger has never displayed any other time than 4am.
If you suspend your computer(s) tonight, what’s the output from those three commands when you wake it/them up tomorrow? Please share tomorrow so that we can compare.
So yeah this looks like its back to normal, now that i haven’t booted. After boot this seems to launch the .timer after 1 hour and then goes back to the schedule
Sources for the timer can be found here:
EDIT: Just to reitarate, we know this is not optimal way of doing this and we have plans to move to the new uupd service at some point (GitHub - ublue-os/uupd)
systemctl status rpm-ostreed-automatic.timer
● rpm-ostreed-automatic.timer - rpm-ostree Automatic Update Trigger
Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed-automatic.timer; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/rpm-ostreed-automatic.timer.d
└─override.conf
Active: active (waiting) since Mon 2025-03-10 07:56:11 CET; 24h ago
Invocation: 09537471b28147acb335ca4afad88fa6
Trigger: Wed 2025-03-12 04:07:30 CET; 19h left
Triggers: ● rpm-ostreed-automatic.service
Docs: man:rpm-ostree(1)
man:rpm-ostreed.conf(5)
Mar 10 07:56:11 aurora systemd[1]: Started rpm-ostreed-automatic.timer - rpm-ostree Automatic Update Trigger.
systemctl status rpm-ostreed-automatic.service
× rpm-ostreed-automatic.service - rpm-ostree Automatic Update
Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed-automatic.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf, 50-keep-warm.conf
/usr/lib/systemd/system/rpm-ostreed-automatic.service.d
└─override.conf
Active: failed (Result: exit-code) since Tue 2025-03-11 08:25:00 CET; 6min ago
Duration: 2.588s
Invocation: eb3d9110e17f40e8a68997ba47345bfa
TriggeredBy: ● rpm-ostreed-automatic.timer
Docs: man:rpm-ostree(1)
man:rpm-ostreed.conf(5)
Process: 368598 ExecCondition=/bin/bash -c [[ "$(busctl get-property org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager Metered | cut -c 3-)" == @(2|4) ]] (code=exited, status=0/SUCCESS)
Process: 368663 ExecStart=rpm-ostree upgrade --quiet --trigger-automatic-update-policy (code=exited, status=1/FAILURE)
Main PID: 368663 (code=exited, status=1/FAILURE)
Mem peak: 8M
CPU: 73ms
Mar 11 08:24:57 aurora systemd[1]: Starting rpm-ostreed-automatic.service - rpm-ostree Automatic Update...
Mar 11 08:24:57 aurora systemd[1]: Started rpm-ostreed-automatic.service - rpm-ostree Automatic Update.
Mar 11 08:25:00 aurora rpm-ostree[368663]: error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: pinging container registry ghcr.io: Get "https://ghcr.io/v2/": dial tcp: lookup ghcr.io: Temporary failure in name resolution
Mar 11 08:25:00 aurora systemd[1]: rpm-ostreed-automatic.service: Main process exited, code=exited, status=1/FAILURE
Mar 11 08:25:00 aurora systemd[1]: rpm-ostreed-automatic.service: Failed with result 'exit-code'.
Your update runs successfully after waking up the PC, my fails.
I’m pretty certain it has to do, again, with the Network Manager that I reported in the other thread: even after unlocking my PC I don’t have an internet connection for a few seconds, after which I get a notification saying I’m connected again. I’m on a wired connection, so it seems the connection should be instant but apparently it’s not.
That scenario (the possibility of being unconnected for a few seconds after wake up) is something to keep in mind with the new update service - a delay should probably be added.