FS#46604 - [bluez] bluez gives an error on startup with kdbus enabled.

Attached to Project: Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Thursday, 08 October 2015, 09:28 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 08 October 2015, 15:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I booted with kdbus. Everything works so far apart from one boot error about bluez.
I don't have any bluetooth devices so this doesn't affect me much but systemd says so I felt I should report it.

systemctl status org.bluez.busname
● org.bluez.busname - DBUS1: org.bluez
Loaded: loaded (/usr/share/dbus-1/system-services/org.bluez.service)
Active: inactive (dead)
Docs: man:systemd-dbus1-generator(8)

Oct 08 11:46:14 hades systemd[1]: org.bluez.busname: Bus service dbus-org.bluez.service not loaded, refusing.
Oct 08 11:46:14 hades systemd[1]: Failed to listen on DBUS1: org.bluez.
Oct 08 11:46:14 hades systemd[1]: org.bluez.busname: Bus service dbus-org.bluez.service not loaded, refusing.
Oct 08 11:46:14 hades systemd[1]: Failed to listen on DBUS1: org.bluez.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 08 October 2015, 15:24 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Thursday, 08 October 2015, 13:47 GMT
Including heftig as linux-zen is the only supported kernel that has kdbus.
Comment by Jan Alexander Steffens (heftig) - Thursday, 08 October 2015, 13:50 GMT
This isn't a bug; applications are trying to access bluez but since bluetooth.service isn't enabled, it fails.

You'll get the same behavior (but different messages) with kdbus disabled, too.
Comment by Hussam Al-Tayeb (hussam) - Thursday, 08 October 2015, 15:23 GMT
Alright, thank you for explaining.
You can close the bug report if you wish then.

Loading...