Bluetooth not connecting to D-Bus after resuming from RAM

.:B:. · 2011-07-22 07:19:56

Since a few days my bluetooth devices are unable to reconnect after resuming from suspend to RAM. The message in /var/log/daemon.log says the bluetooth daemon can't connect to D-Bus:

bluetoothd[11819]: Unable to get on D-Bus

It speaks for itself that it worked before . I have set pm-utils to stop bluetooth on suspend and start it on resume - 10 seconds after resuming - but that does not work. So far the only thing that works (without requiring half a minute, so to speak, to get my system functional again) is restarting D-Bus and bluetooth afterwards. I have pm-utils doing that now, and that works fine, but I guess it's supposed to work without hacking...

Any pointers?

YavkatA · 2011-07-30 23:37:29

I have a similar problem. In my case bluetoothd segfaults. Running Arch x86_64 with testing repos disabled.

[48101.115558] EXT4-fs (sda1): re-mounted. Opts: commit=0
[48101.121614] EXT4-fs (sda2): re-mounted. Opts: commit=0
[48101.200863] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[48101.207485] r8169 0000:03:00.0: eth0: link down
[48101.207491] r8169 0000:03:00.0: eth0: link down
[48101.208438] bluetoothd[11010]: segfault at 2345b3b199 ip 00007fd89941fd8a sp 00007fff2d275828 error 4 in libc-2.14.so[7fd8993a5000+157000]
[48101.216466] ADDRCONF(NETDEV_UP): eth0: link is not ready
[48102.847870] r8169 0000:03:00.0: eth0: link up
[48102.848293] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[48113.265227] eth0: no IPv6 routers present

Any help would be greatly appreciated.

jasonwryan · 2011-07-31 09:26:45

Yavkata - please don't hijack threads: if you can't help the OP with his issue, start your own thread.

Arch Linux

#1 2011-07-22 07:19:56

Bluetooth not connecting to D-Bus after resuming from RAM

#2 2011-07-30 23:37:29

Re: Bluetooth not connecting to D-Bus after resuming from RAM

#3 2011-07-31 09:26:45

Re: Bluetooth not connecting to D-Bus after resuming from RAM

Board footer