Universal Blue•4mo ago

View update schedule

How does the automatic rpm-ostree update work under the hood? I'm looking for the rough equivalent of systemctl status dnf-automatic to see (1) when it's supposed to check and (2) whether the most recent check succeeded

Solution:

systemctl status ublue-update.timer

Jump to solution

4 Replies

aednichols•4mo ago

I did start with the docs [0] 😄 but struck out [0] https://universal-blue.discourse.group/t/updates-rollback-and-rebasing-on-bazzite/36#desktop-images-4

Universal Blue

Updates, Rollback, and Rebasing on Bazzite

Attention: Do not rebase between different desktop environments. Video Guide Updates How do updates work? Note: Bazzite is still in its early stages, so updates may happen frequently. Bazzite updates all of the changes made specifically in Bazzite itself, updates from Fedora’s base packages upstream, and most user installed a...

wolfyreload•4mo ago

The ujust toggle-updates command in the terminal turns the auto updates on or off. Underneath Bazzite is using topgrade for updating all the software on your system. It runs by default 20 minutes after your system has booted or after 6 hours of low activity

Solution

Kyle Gospo•4mo ago

systemctl status ublue-update.timer

aednichols•4mo ago

OK sweet, this led me to what I was looking for. Thanks!

aednichols@spatium ~> systemctl status ublue-update
○ ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Wed 2024-05-29 02:19:23 EDT; 2min 36s ago
TriggeredBy: ● ublue-update.timer
    Process: 221545 ExecStart=/usr/bin/ublue-update (code=exited, status=0/SUCCESS)
   Main PID: 221545 (code=exited, status=0/SUCCESS)
        CPU: 409ms

May 29 02:19:12 spatium systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,333] ublue_update.update_checks.system:INFO | No system update available.
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,333] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,334] ublue_update.cli:INFO | System passed all update checks
May 29 02:19:15 spatium ublue-update[221545]: [2024-05-29 02:19:15,663] ublue_update.cli:INFO | Running update for user: 'aednichols'
May 29 02:19:15 spatium sudo[221757]:     root : PWD=/ ; USER=aednichols ; ENV=DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 DBUS_SESSION_BUS_ADDRESS=unix:path=/ru>
May 29 02:19:23 spatium ublue-update[221545]: [2024-05-29 02:19:23,262] ublue_update.cli:INFO | System update complete
May 29 02:19:23 spatium systemd[1]: ublue-update.service: Deactivated successfully.
May 29 02:19:23 spatium systemd[1]: Finished ublue-update.service - Universal Blue Update Oneshot Service.

aednichols@spatium ~> systemctl status ublue-update
○ ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Wed 2024-05-29 02:19:23 EDT; 2min 36s ago
TriggeredBy: ● ublue-update.timer
    Process: 221545 ExecStart=/usr/bin/ublue-update (code=exited, status=0/SUCCESS)
   Main PID: 221545 (code=exited, status=0/SUCCESS)
        CPU: 409ms

May 29 02:19:12 spatium systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,333] ublue_update.update_checks.system:INFO | No system update available.
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,333] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,334] ublue_update.cli:INFO | System passed all update checks
May 29 02:19:15 spatium ublue-update[221545]: [2024-05-29 02:19:15,663] ublue_update.cli:INFO | Running update for user: 'aednichols'
May 29 02:19:15 spatium sudo[221757]:     root : PWD=/ ; USER=aednichols ; ENV=DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 DBUS_SESSION_BUS_ADDRESS=unix:path=/ru>
May 29 02:19:23 spatium ublue-update[221545]: [2024-05-29 02:19:23,262] ublue_update.cli:INFO | System update complete
May 29 02:19:23 spatium systemd[1]: ublue-update.service: Deactivated successfully.
May 29 02:19:23 spatium systemd[1]: Finished ublue-update.service - Universal Blue Update Oneshot Service.

Gaming

Programming

View update schedule