Bug#587158: bluetoothd: No DBus connection

[Thomas Themel]

Package: bluez
Version: 4.66-1
Severity: important

Hi,

I can't pair Bluetooth devices with the latest version of bluez.
bluetooth-agent fails with

themel@kallisti:~$ bluetooth-agent 1234
Can't get default adapter
The name org.bluez was not provided by any .service files

Indeed, org.bluez is not on the system DBus. When I start
bluetoothd -nd as root while watching with QDBusViewer, I see it appear
and quickly disappear. A dbus-monitor trace confirms that it pops up,

signal sender=org.freedesktop.DBus -> dest=(null destination) serial=7 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
string ":1.57"
string ""
string ":1.57"

- registers its service name -

signal sender=org.freedesktop.DBus -> dest=(null destination) serial=8 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
string "org.bluez"
string ""
string ":1.57"

then emits a lot of signals before disappearing a fraction of a second later:

signal sender=org.freedesktop.DBus -> dest=(null destination) serial=9 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
string "org.bluez"
string ":1.57"
string ""
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=10 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
string ":1.57"
string ":1.57"
string ""

-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bluez depends on:
ii dbus 1.2.24-1 simple interprocess messaging syst
ii libbluetooth3 4.63-2 Library to use the BlueZ Linux Blu
ii libc6 2.11.1-3 Embedded GNU C Library: Shared lib
ii libcap-ng0 0.6.3-1 An alternate posix capabilities li
ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst
ii libglib2.0-0 2.24.1-1 The GLib library of C routines
ii libnl1 1.1-5 library for dealing with netlink s
ii libusb-0.1-4 2:0.1.12-15 userspace USB programming library
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
ii makedev 2.3.1-89 creates device files in /dev
ii module-init-tools 3.12~pre2-3 tools for managing Linux kernel mo
ii udev 157-1 /dev/ and hotplug management daemo

bluez recommends no packages.

Versions of packages bluez suggests:
ii python-dbus 0.83.1-1 simple interprocess messaging syst
ii python-gobject 2.21.1-2 Python bindings for the GObject li

-- Configuration Files:
/etc/bluetooth/rfcomm.conf changed [not included]

-- no debconf information

--
[*Thomas Themel*] "It's like watching somebody build a building downtown
[extended contact] - anywhere - they always dig down to bedrock and then go up.
[info provided in] If you don't do that first, it's just going to fall over."
[*message header*] - James Gosling on security design

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[step...@shimaore.net]

Hi,

I had the same issue ("bluetoothd[]: D-Bus setup failed: Connection is
not allowed to own the service "org.bluez" due to security policies in
the configuration file file").

The root cause of the issue seems to be that the configuration file

/etc/dbus-1/system.d/bluetooth.conf

was missing on my system. (etckeeper reports that the file was removed on
2017-07-05, if that's any help.)

For the record, this could not be resolved by doing

aptitude reinstall bluez

or the equivalent sequence (remove + install); these did not reinstall
the missing file.

I corrected by doing

aptitude purge bluez
aptitude install bluez

The former version on my system (reported during the purge operation) was
bluez (5.47-1), although this probably is not the version that caused
the problem.
S.