FS#61386 - [bluez] bluetooth.conf not found by D-Bus

Attached to Project: Arch Linux
Opened by David Spicer (azleifel) - Sunday, 13 January 2019, 22:24 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 14 January 2019, 06:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 17
Private No

Details

Description:

For bluez 5.50-5, the bluetooth.conf file has been moved to /usr/share/dbus-1/dbus-1/system.d/, with the result that it doesn't get found and bluetoothd fails to start:

Jan 13 21:48:41 desktop-one bluetoothd[804]: Bluetooth daemon 5.50
Jan 13 21:48:41 desktop-one bluetoothd[804]: D-Bus setup failed: Connection ":1.5" is not allowed to own the service "org.bluez" due to security policies in the configuration file
Jan 13 21:48:41 desktop-one bluetoothd[804]: Unable to get on D-Bus
Jan 13 21:48:55 desktop-one systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Jan 13 21:48:55 desktop-one systemd[1]: bluetooth.service: Failed with result 'exit-code'.

Moving bluetooth.conf to /usr/share/dbus-1/system.d fixes the problem.

Additional info:
* bluez 5.50-5

Steps to reproduce: Update to bluez 5.50-5 and reboot.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 14 January 2019, 06:17 GMT
Reason for closing:  Fixed
Comment by tinywrkbee (tinywrkbee) - Sunday, 13 January 2019, 22:37 GMT
Changing build flag to --with-dbusconfdir=/usr/share solves this for me and everything looks in place

# pacman -Ql bluez bluez-libs bluez-utils |grep /usr/share/
bluez /usr/share/
bluez /usr/share/dbus-1/
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
bluez /usr/share/dbus-1/system.d/
bluez /usr/share/dbus-1/system.d/bluetooth.conf
bluez /usr/share/doc/
bluez /usr/share/doc/bluez/
bluez /usr/share/doc/bluez/dbus-apis/
bluez /usr/share/doc/bluez/dbus-apis/adapter-api.txt
bluez /usr/share/doc/bluez/dbus-apis/advertising-api.txt
bluez /usr/share/doc/bluez/dbus-apis/agent-api.txt
bluez /usr/share/doc/bluez/dbus-apis/assigned-numbers.txt
bluez /usr/share/doc/bluez/dbus-apis/btmon.txt
bluez /usr/share/doc/bluez/dbus-apis/btsnoop.txt
bluez /usr/share/doc/bluez/dbus-apis/device-api.txt
bluez /usr/share/doc/bluez/dbus-apis/gatt-api.txt
bluez /usr/share/doc/bluez/dbus-apis/health-api.txt
bluez /usr/share/doc/bluez/dbus-apis/input-api.txt
bluez /usr/share/doc/bluez/dbus-apis/media-api.txt
bluez /usr/share/doc/bluez/dbus-apis/mgmt-api.txt
bluez /usr/share/doc/bluez/dbus-apis/network-api.txt
bluez /usr/share/doc/bluez/dbus-apis/obex-agent-api.txt
bluez /usr/share/doc/bluez/dbus-apis/obex-api.txt
bluez /usr/share/doc/bluez/dbus-apis/pics-opp.txt
bluez /usr/share/doc/bluez/dbus-apis/pixit-opp.txt
bluez /usr/share/doc/bluez/dbus-apis/profile-api.txt
bluez /usr/share/doc/bluez/dbus-apis/pts-opp.txt
bluez /usr/share/doc/bluez/dbus-apis/sap-api.txt
bluez /usr/share/doc/bluez/dbus-apis/settings-storage.txt
bluez /usr/share/doc/bluez/dbus-apis/supported-features.txt
bluez /usr/share/doc/bluez/dbus-apis/test-coverage.txt
bluez /usr/share/doc/bluez/dbus-apis/test-runner.txt
bluez /usr/share/man/
bluez /usr/share/man/man8/
bluez /usr/share/man/man8/bluetoothd.8.gz
bluez-utils /usr/share/
bluez-utils /usr/share/man/
bluez-utils /usr/share/man/man1/
bluez-utils /usr/share/man/man1/bccmd.1.gz
bluez-utils /usr/share/man/man1/btattach.1.gz
bluez-utils /usr/share/man/man1/l2ping.1.gz
bluez-utils /usr/share/man/man1/rctest.1.gz
Comment by David Spicer (azleifel) - Sunday, 13 January 2019, 22:53 GMT
I've just rebuilt bluez with --with-dbusconfdir=/usr/share and everything seems to be working fine here too.
Comment by Anton Antons (insecuriy) - Monday, 14 January 2019, 01:54 GMT
Thank you for the tip @tinywrkbee, highly appreciated.
Comment by Eric G (madmangun) - Monday, 14 January 2019, 04:14 GMT
Thank you @tinywrkbee, worked like a charm.

Loading...