-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] error: Bus owner changed, aborting. This likely means the daemon crashed #4975
Comments
If anyone has a similar issue to what I have, I made a simple bash script to workaround it, here it is for would it be of use to anyone else (it basically loops given command until it exits successfully):
|
Yes, this looks like the same issue as #4966. Let's track that one instead. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When running rpm-ostree upgrade / install / uninstall / update I get almost every time:
error: Bus owner changed, aborting. This likely means the daemon crashed; check logs with journalctl -xe.
Full journalctl -xe output:
https://pastebin.com/YzqRf72e
Reproduction steps
What I did to reproduce this in a Boxes vm is the following:
Note: I only succeeded to reproduce it ones.
rpm-ostree install btop distrobox gparted guestfs-tools libvirt-daemon-config-network libvirt-daemon-kvm openrgb python3-libguestfs qemu-kvm steam-devices timeshift virt-install virt-manager virt-top virt-viewer zsh
2.1
sudo rpm-ostree kargs \ --append-if-missing="intel_iommu=on" \ --append-if-missing="iommu=pt" \ --append-if-missing="rd.driver.pre=vfio_pci" \ --reboot
2.2
sudo rpm-ostree initramfs \ --enable \ --arg="--add-drivers" \ --arg="vfio-pci" \ --reboot
after the last step I get the error: Bus owner changed, aborting. This likely means the daemon crashed; check logs with
journalctl -xe
.Expected behavior
rpm-ostree upgrade / installs / uninstalls successfully
Actual behavior
It usually go's as follows:
System details
Additional information
I still sometimes succeed to upgrade my system after enough reboots I would estimate my success rate on my actual system to be ~1/50.
Also I use ext4 instead of btrs if that's of any important's in this case.
Maybe related to #4966 ?
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: