So here are the morning stats
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 17:23:23 EET; 13h ago
Invocation: ecebd8a65eef464a808acdde54413b34
Trigger: Wed 2025-03-12 04:01:40 EET; 21h left
Triggers: ● rpm-ostreed-automatic.service
Docs: man:rpm-ostree(1)
man:rpm-ostreed.conf(5)
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: inactive (dead) (Result: exec-condition) since Tue 2025-03-11 06:52:23 EET; 2min 6s ago
Duration: 1.669s
Invocation: 6e704223fa904bc0924dfddcdeff0b83
TriggeredBy: ● rpm-ostreed-automatic.timer
Condition: start condition unmet at Tue 2025-03-11 06:52:23 EET; 2min 6s ago
Docs: man:rpm-ostree(1)
man:rpm-ostreed.conf(5)
Process: 21497 ExecCondition=/bin/bash -c [[ "$(busctl get-property org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.>
Mem peak: 2M
CPU: 9ms
Mar 11 06:52:23 neptune systemd[1]: Starting rpm-ostreed-automatic.service - rpm-ostree Automatic Update...
Mar 11 06:52:23 neptune systemd[1]: rpm-ostreed-automatic.service: Skipped due to 'exec-condition'.
Mar 11 06:52:23 neptune systemd[1]: Condition check resulted in rpm-ostreed-automatic.service - rpm-ostree Automatic Update being skipped.
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-dx:latest
Digest: sha256:cfdead231281fe47da210f45ac70b5129e27e088769dc4e176e0375b50b881f3
Version: latest-41.20250310 (2025-03-10T05:06:01Z)
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:latest
Digest: sha256:22904bf0e15e0d1c0ac44c79567addaa9c921ba92b9521d2f89b3ffbcb9e03b2
Version: latest-41.20250309.2 (2025-03-09T10:30:34Z)
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:latest
Digest: sha256:4f5c8103eaf87c6cad1e53334b9c7eae864e03abc21df619269661783e378b6f
Version: latest-41.20250213.1 (2025-02-13T06:28:37Z)
Pinned: yes
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)