Universal BlueUB
Universal Blue•2y ago
Nnubes256

rpm-ostree troubles (InterruptedLiveCommit)

Hello, I was installing new packages on my Bazzite install using rpm-ostree install --apply-live (which did not have a Flatpak and cannot be installed onto a Distrobox without pulling the entirety of KDE). However, as it was finishing, this happened:

[...]
Will download: 7 packages (13.7 MB)
Downloading from 'updates'... done
Downloading from 'fedora'... done
Importing packages... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 135.2 MB (pkgcache branches: 0)
Computing /etc diff to preserve... done
error: Bus owner changed, aborting. This likely means the daemon crashed; check logs with `journalctl -xe`.


Indeed, upon checking the systemd journal, 
rpm-ostree
 had an abort and proceeded to coredump. Upon checking rpm-ostree status, now it's like this:

State: idle
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:349ddc3efa844187ca3b7f1ae16c880b00e18aaabf995d876ee6bf36554d22c0
                  Version: 40.20240505.0 (2024-05-05T05:45:58Z)
                     Diff: 7 added
          LayeredPackages: cdemu-client cdemu-daemon k3b kde-cdemu-manager-kf6 mingw32-gdb strace

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:349ddc3efa844187ca3b7f1ae16c880b00e18aaabf995d876ee6bf36554d22c0
                  Version: 40.20240505.0 (2024-05-05T05:45:58Z)
    InterruptedLiveCommit: 2d2c341bc88bc990ba63dc0e74d441f1d833f7207acaa4cb74273d37e77d3d2d
          LayeredPackages: cdemu-client cdemu-daemon kde-cdemu-manager-kf6 mingw32-gdb strace
                 Unlocked: transient

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:349ddc3efa844187ca3b7f1ae16c880b00e18aaabf995d876ee6bf36554d22c0
                  Version: 40.20240505.0 (2024-05-05T05:45:58Z)

I tried to do a rpm-ostree cleanup -p in hopes this would revert me to the previous state, but that only removed the first image, leaving the current (interrupted) one and the one without layered packages, so now it's like this:

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:349ddc3efa844187ca3b7f1ae16c880b00e18aaabf995d876ee6bf36554d22c0
                  Version: 40.20240505.0 (2024-05-05T05:45:58Z)
    InterruptedLiveCommit: 2d2c341bc88bc990ba63dc0e74d441f1d833f7207acaa4cb74273d37e77d3d2d
          LayeredPackages: cdemu-client cdemu-daemon kde-cdemu-manager-kf6 mingw32-gdb strace
                 Unlocked: transient

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:349ddc3efa844187ca3b7f1ae16c880b00e18aaabf995d876ee6bf36554d22c0
                  Version: 40.20240505.0 (2024-05-05T05:45:58Z)


I also did an ostree fsck, and this reported corrupted objects. However, I saw this was a known issue with container-based distros.

So, should I be worried, or could I just rpm-ostree rollback and move on? I'd like to avoid removing all layered packages since rpm-ostree install always takes ages to do anything.
Solution
TL;DR: A rpm-ostree rollback does seem to fix it. I'm going to wait and see whether the crash problem is transient or not.
EDIT: yep, transient problem. Fixed!
Jump to solution
Was this page helpful?