Failed to start dbus System Message Bus

Support
, ,
1

After a recent update dbus is now broken on my system and consequently many other services such as nvidia drivers and network manager have broken. Interestingly, I can run startxfce4 as root but it fails to launch as any other user.

The update was from the unstable branch however after this issue started I connected to the internet without NetworkManager and switched to the stable branch to perform an update.

sudo systemctl status dbus returns:
Failed to start dbus System Message Bus

sudo systemctl journal | grep "dbus" returns:

dbus-broker-launch[1051]: ERROR run @ ../dbus-broker-36/src/launch/main.c  +152: Return code 1
dbus-broker-launch[1051]:        main @ ../dbus-broker-36/src/launch/main.c +178
dbus-broker-launch[1051]: Exiting due to fatal error: -131

I received a similar message but with a different file before, so I tried moving that file to my home folder and now it returns the same error but with the above message.

Today I tried updating the system, however this failed returning the error that these files exists in filesystem

Any help is greatly appreciated, thanks.

2

Hi @megalomart, and welcome!

I’m by no means an expert, but this is what I’d have done in the same situation:

  1. Boot from a relatively new live ISO, and from there enter a chroot environment.

How to chroot

  1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

  2. Write/copy/dd the ISO to a USB thumb drive.

  3. When done, boot with the above mentioned USB thumb drive into the live environment.

  4. Once booted, open a terminal and enter the following command to enter the chroot environment:

manjaro-chroot -a
  1. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.

(Note: by no means am I sure this step would be neeccessary, but it is what I would’ve done.)
3. Within the # How to chroot

  1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

  2. Write/copy/dd the ISO to a USB thumb drive.

  3. When done, boot with the above mentioned USB thumb drive into the live environment.

  4. Once booted, open a terminal and enter the following command to enter the chroot environment:

manjaro-chroot -a
  1. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.

Within the chroot environment, reinstall dbus-broker and dbus-broker-units, overwriting existing files:

pamac install dbus-broker dbus-broker-units --overwrite='/usr/bin/dbus-broker,/usr/bin/dbus-broker-launch,/usr/lib/systemd/catalog/*,/usr/lib/systemd/*'

I don’t knows if it will, but I hope it helps!

1 Like
3

Thanks for the reply. Unfortunately the same issue persists.

4

Fixed by entering chroot and running the following:

sudo pacman -Syyu --overwrite "*"
sudo paccache -r
sudo pacman -Scc
sudo pacman -Syy
sudo pacman -Syu
5

If you apply

sudo pacman -Scc

then

sudo paccache -r

was useless as it simply removed only a part of what the second command removed.

You had updated already with your first command, so completely without any effect. Anyway, instead of this you could have better used

sudo pacman -Syyu
6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.