Discussion:
Bluetooth not working
(too old to reply)
James H. Markowitz
2019-08-29 14:25:32 UTC
Permalink
When I try to start the Bluetooth daemon in Slack64 14.2, by
means of /etc/rc.d/rc.bluetooth start, I get the following in /var/log/
messages:

Aug 29 08:19:36 xyz bluetoothd[27808]: Bluetooth daemon 5.47
Aug 29 08:19:36 xyz dbus[1200]: [system] Rejected send message, 2 matched
rules; type="method_call", sender=":1.388" (uid=1000 pid=30712 comm="/usr/
bin/pulseaudio --start --log-target=syslog ")
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects"
error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0
pid=27808 comm="/usr/sbin/bluetoothd ")
Aug 29 08:19:36 xyz bluetoothd[27808]: Starting SDP server
Aug 29 08:19:36 xyz bluetoothd[27808]: Bluetooth management interface
1.10 initialized

After this, any attempts to launch the Bluetooth manager from the
XFCE menus elicits the dbus[1200] line above several times. The Bluetooth
manager just seems to hang there forever, in the background.

Any ideas as to what is going on, and how to sort this out?
K. Venken
2019-08-29 14:33:36 UTC
Permalink
Post by James H. Markowitz
When I try to start the Bluetooth daemon in Slack64 14.2, by
means of /etc/rc.d/rc.bluetooth start, I get the following in /var/log/
Aug 29 08:19:36 xyz bluetoothd[27808]: Bluetooth daemon 5.47
Aug 29 08:19:36 xyz dbus[1200]: [system] Rejected send message, 2 matched
rules; type="method_call", sender=":1.388" (uid=1000 pid=30712 comm="/usr/
bin/pulseaudio --start --log-target=syslog ")
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects"
error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0
pid=27808 comm="/usr/sbin/bluetoothd ")
Aug 29 08:19:36 xyz bluetoothd[27808]: Starting SDP server
Aug 29 08:19:36 xyz bluetoothd[27808]: Bluetooth management interface
1.10 initialized
After this, any attempts to launch the Bluetooth manager from the
XFCE menus elicits the dbus[1200] line above several times. The Bluetooth
manager just seems to hang there forever, in the background.
Any ideas as to what is going on, and how to sort this out?
It have the impression that there is something wrong with messagebus
and/or pulseaudio and bluetooth has a dependency on it. Is rc.messagebus
and/or pulseaudio started? If not, try starting these first.

Loading...