[Feisty] bluez-utils update hangs on stopping bluetooth service

little hack to bring the system into a consistent state:

i put an "exit 0" at the beginning of /etc/init.d/bluetooth and then reinstalled the package

Confirmed on my fresh installed Feisty Herd 4 system.

ASUS Mainboard A7N8X ACPI BIOS Rev. 1007
AMD AthlonXP 1800+
ATI Radeon 8500

P.S. I don't have any bluetooth hardware, too.

 status confirmed

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.

Same problem here - on Gusty Gibon (beta) - 7.10 Beta

Try to make a normal update. Upgrade package process hangs for bluez-utils if trying to stop the bluetooth service.

"Removing bluez-utils ...
 * Stopping Bluetooth services "

Also on this machine not bluetooth hardware is installed or available.

This is critical in a sense as no longer updates are possible. Also forcing to remove the package hangs as it try to stop the service

This now happening with Feisty --> Gutsy upgrades.

Milestoning as this breaks upgrade to Gutsy.

My update from Feisty to Gutsy release candidate by update-manager -d -command was jammed by this bug, package installation hanging at "Stopping bluetooth services". I didn't want to do a clear install so I messed around and tried to find a way to get forward. In the end, killing dpkg -process allowed for the update to proceed.

After that, there came ~15 error messages about missing dependencies, because of the failed package install, but nothing critical.

I was able to finish the update and rebooted. Afterwards everything is good except for update manager complaining about the broken packages. Because I don't have any bluetooth hardware, I disabled the bluetooth script using the tip by Kai Scroeder earlier in this report.

> little hack to bring the system into a consistent state:
> i put an "exit 0" at the beginning of /etc/init.d/bluetooth

After that I rebooted, and ran "sudo apt-get install -f" which fixed the update.
Hope this helps somebody! : )

I have this problem as well during the 7.04 to 7.10 upgrade. I tried booting off the Live CD of 7.10 and it still hang at bluetooth initialization. My workaround to this was to unplug my USB flash card reader and I was able to proceed with the installation.

Adding line "exit 0" in Hardy don't do the thing, "exit 0" is already on the last line. Cannot remove, repair, reinstall and do anything with those package...

Hi, this bug should be fixed in the latest Intrepid release candidate. Would you mind downloading a LiveCD and testing to see if it still occurs for you?

Hi Mario, today i updated a new installed 8.04 to 8.10 and i have the same issue.

I think that isn't related with bluez, because if i tried for example do a "ps ax" i see a few lines and after that
the terminals hangs, similar than when you try a "df -h" and see some lines and the system is waiting for something.
I can open other terminals but if i tried "ps ax" in that i lose that and need reopen a new one.

----------
I comment the next because possible can help you, i know that should not be in this bug:

I passed to intrepid for try the xen kernel with nvidia support, but i see some errors related with module python and
continue the boot, and i dont see any more the screen is black. I can login with ssh and i arrive to the goal, i have
compiled and loaded the nvidia kernel module, but i need first fix the black screen issue for see nvidia and xen working
again like old times :-D

Mother board with video integrated: ALIVENF7G-HDREADY

Still hangs with 8.10 live cd while trying to start/stop bluetooth...

I had this bug updating from Hardy to Intrepid today. I think the first time it just hung on "Stopping Bluetooth Services". I was doing the upgrade over SSH, so I closed the session (I couldn't fix it by using Ctrl+C to stop the update configuring like you can when most other ones hang). When I logged back in and did a 'sudo dpkg --configure -a' it got a bit further, hanging on 'Starting Bluetooth Services". I used Kai's hack to fix it, as I don't have bluetooth.

Latest version of the init script (karmic) will just issue a pkill to stop the process and won't hang if it's not getting stopped. Marking the bug as fixed.