Failed to start dbus System Message Bus

Support
, ,
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