Universal BlueUB
Universal Blue•2y ago
Geechan

ublue-update process fails with exit code

For the past few days, I've been having errors with the automatic ublue-update service crashing before it can perform any updates. As a result, automatic updates never apply, and I have to manually update my system (which works without issue).

Here's a relevant journal log:

 4月 27 17:20:14 minato-san systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
 4月 27 17:20:24 minato-san ublue-update[32763]: [2024-04-27 17:20:24,514] ublue_update.update_checks.system:INFO | System update available.
 4月 27 17:20:24 minato-san ublue-update[32763]: [2024-04-27 17:20:24,514] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
 4月 27 17:20:24 minato-san ublue-update[32763]: [2024-04-27 17:20:24,515] ublue_update.cli:INFO | System passed all update checks
 4月 27 17:20:24 minato-san sudo[32878]:     root : PWD=/ ; USER=geechan ; ENV=DISPLAY=:0 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/notify-send 'System Updater' 'System passed checks, updating ...' '--app-name=Universal Bl>
 4月 27 17:20:24 minato-san ublue-update[32763]: Traceback (most recent call last):
 4月 27 17:20:24 minato-san ublue-update[32763]:   File "/usr/bin/ublue-update", line 8, in <module>
 4月 27 17:20:24 minato-san ublue-update[32763]:     sys.exit(main())
 4月 27 17:20:24 minato-san ublue-update[32763]:              ^^^^^^
 4月 27 17:20:24 minato-san ublue-update[32763]:   File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 240, in main
 4月 27 17:20:24 minato-san ublue-update[32763]:     run_updates(cli_args.system, system_update_available)
 4月 27 17:20:24 minato-san ublue-update[32763]:   File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 118, in run_updates
 4月 27 17:20:24 minato-san ublue-update[32763]:     out = subprocess.run(
 4月 27 17:20:24 minato-san ublue-update[32763]:           ^^^^^^^^^^^^^^^
 4月 27 17:20:24 minato-san ublue-update[32763]:   File "/usr/lib64/python3.12/subprocess.py", line 548, in run
 4月 27 17:20:24 minato-san ublue-update[32763]:     with Popen(*popenargs, **kwargs) as process:
 4月 27 17:20:24 minato-san ublue-update[32763]:          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 4月 27 17:20:24 minato-san ublue-update[32763]:   File "/usr/lib64/python3.12/subprocess.py", line 1026, in __init__
 4月 27 17:20:24 minato-san ublue-update[32763]:     self._execute_child(args, executable, preexec_fn, close_fds,
 4月 27 17:20:24 minato-san ublue-update[32763]:   File "/usr/lib64/python3.12/subprocess.py", line 1953, in _execute_child
 4月 27 17:20:24 minato-san ublue-update[32763]:     raise child_exception_type(errno_num, err_msg, err_filename)
 4月 27 17:20:24 minato-san ublue-update[32763]: PermissionError: [Errno 13] Permission denied: '/usr/libexec/ublue-system-update.py'
 4月 27 17:20:24 minato-san systemd[1]: ublue-update.service: Main process exited, code=exited, status=1/FAILURE
 4月 27 17:20:24 minato-san systemd[1]: ublue-update.service: Failed with result 'exit-code'.
 4月 27 17:20:24 minato-san systemd[1]: Failed to start ublue-update.service - Universal Blue Update Oneshot Service.
Solution
Forgot to update this. This was solved by changing to the signed build instead of the unsigned build. rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Jump to solution
Was this page helpful?