Arch Linux

alf9000

Member

Registered: 2019-02-20

Posts: 9

[pentium4] bluetooth.service - D-Bus setup failed

After migration to pentium4 I receive following error on bluetooth.service start:

$ sudo systemctl restart bluetooth.service
Job for bluetooth.service failed because the control process exited with error code.
See "systemctl status bluetooth.service" and "journalctl -xe" for details.

$ sudo journalctl -u bluetooth.service
May 05 10:44:06 n systemd[1]: Starting Bluetooth service...
May 05 10:44:06 n bluetoothd[24821]: Bluetooth daemon 5.50
May 05 10:44:07 n bluetoothd[24821]: D-Bus setup failed: Connection ":1.189" is not allowed to own the service "org.bluez" due to security policies in the configuration file
May 05 10:44:07 n bluetoothd[24821]: Unable to get on D-Bus
May 05 10:44:07 n systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE
May 05 10:44:07 n systemd[1]: bluetooth.service: Failed with result 'exit-code'.
May 05 10:44:07 n systemd[1]: Failed to start Bluetooth service.

I think we had to modify something in /usr/share/dbus-1/dbus-1/system.d/bluetooth.conf ?

Edit:

$ sudo pacman -Q bluez
bluez 5.50-5.0

$ sudo pacman -Ql bluez | egrep -i dbus-1
bluez /usr/share/dbus-1/
bluez /usr/share/dbus-1/dbus-1/
bluez /usr/share/dbus-1/dbus-1/system.d/
bluez /usr/share/dbus-1/dbus-1/system.d/bluetooth.conf
bluez /usr/share/dbus-1/services/
bluez /usr/share/dbus-1/services/org.bluez.obex.service
bluez /usr/share/dbus-1/system-services/
bluez /usr/share/dbus-1/system-services/org.bluez.service

The double dbus-1/dbus-1 is the error.
https://bbs.archlinux.org/viewtopic.php?id=243400 sounds like a bluez 5.50-6 will fix it.

Workaround:

sudo cp /usr/share/dbus-1/dbus-1/system.d/bluetooth.conf /usr/share/dbus-1/system.d/bluetooth.conf
sudo chmod 644 /usr/share/dbus-1/system.d/bluetooth.conf
sudo systemctl restart bluetooth.service

Last edited by alf9000 (2019-05-05 10:23:14)

redqueen

Member

Registered: 2017-12-27

Posts: 21

Re: [pentium4] bluetooth.service - D-Bus setup failed

Have the same problem.
The package isn't actual updated. Its still 5.50-5.0!

Last edited by redqueen (2019-07-25 13:29:20)