I had this problem too (i.e. the hang when the bluetooth service is stopped - I regard the package issues mentioned earlier as an essentially unrelated side-effect). When the system hangs this way, I note messages like this in the system log:
Apr 20 02:49:54 kat hcid[6173]: Can't connect to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Apr 20 02:50:29 kat last message repeated 7 times Apr 20 02:50:59 kat last message repeated 6 times Since I also don't have any bluetooth hardware, my first attempt to work around it was to disable the /etc/init.d/bluetooth script entirely. However that apparently only moved the problem; after that I often got a hang when the dbus service is stopped instead, just like in bug #96100. Judging from the messages, it looks like the problem is that the dbus service is stopped too early instead. So I've now moved the dbus stop script in runlevels 0, 1 and 6 from K12dbus to K99dbus, and I haven't seen this bug since (with the bluetooth script enabled again). Because it looks like a dbus bug, I comment on it further in bug #96100. -- [Feisty] bluez-utils update hangs on stopping bluetooth service https://bugs.launchpad.net/bugs/78690 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
