BlueBuildB
BlueBuild•12mo ago
OceanBby

ublue-update failed with result 'exit-code'

Found this issue https://github.com/ublue-os/ublue-update/issues/113 and some discussion in channels. But the issue is still existed for me. I use Bazzite as the base image, and ujust update works perfectly fine. Anyone else have the same issue?

Also saw devs said they might replace it with this in the future: https://github.com/ublue-os/uupd

ublue-update[47861]: ublue_update.update_checks.system:INFO | System update available.
ublue-update[47861]: ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
ublue-update[47861]: ublue_update.update_inhibitors.custom:INFO | System passed custom checks
ublue-update[47861]: ublue_update.cli:INFO | System passed all update checks
systemd[1]: ublue-update.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: ublue-update.service: Failed with result 'exit-code'.
systemd[1]: Failed to start ublue-update.service - Universal Blue Update Oneshot Service.
GitHub
U-Blue Update Systemd service reports failure when sucessfully run ...
Checking the status it reports a failure exit code, though all of the checks appear to succeed: Brian@fedora ~> systemctl status ublue-update.service × ublue-update.service - Universal Blue Upda...
GitHub
GitHub - ublue-os/uupd
Contribute to ublue-os/uupd development by creating an account on GitHub.
Solution
After lots of messing around, by changing image-vendor and image-ref in /usr/share/ublue-os/image-info.json to my own repo seems fix this so far, had a few successful updates
Jump to solution
Was this page helpful?