Auto update stopped working?

Aurora
8

I may have celebrated too soon.

The two previous commands give:

❯ 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.

1 Like