It happens to me with the same effect, but only after a hibernate/restore cycle. It appears that bluetooth subsystem is started from /etc/init.d/bluetooth via sending a Dbus message to the bluetooth subsystem. For some reason /sbin/bluetoothd fails to start. /etc/init.d/bluetooth stop and then start cycle has no effect either. Only when I manually start bluetoothd everything starts working.
-- /usr/sbin/bluetoothd doesn't get started automatically https://bugs.launchpad.net/bugs/589464 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
