bluetooth start script hangs on HP pavillion dv6700t

[Matthew Smith]

Binary package hint: bluez-utils

Bug submission caveated by the fact that I am a relative noob to Linux.

Hardy Heron 64-bit alternate install desktop CD used.

HARDWARE (HP Pavillion dv6700t)
Intel Core 2 Duo Pprocessor T7250 (2.00 GHz, 2 MB L2 Cache, 800MHz FSB)
4GB DDR2 System Memory (2 Dimm)
NVIDIA GeForce 8400M GS
Fingerprint Reader + Webcam + Microphone
120GB 5400RPM SATA Hard Drive
SuperMulti 8X DVD+/-R/RW with Double Layer Support
(no bluetooth device)

When I attempt to boot the live CD or run an installed distro (installed using the alternate CD), the bluetooth start script hangs. The screen (boot options quiet and splash removed for a known Nvidia video driver problem) shows "starting bluetooth" and does nothing else.

From the command line I changed the name of S25bluetooth to s25bluetooth (thereby essentially hiding it, as I understand it) and the boot process works like a champ. I'll update this some more debug info if I can.

[sasanf (sasanforghani)]

How did you change the name? I have an HP dv9700t and when the bootup process is at starting bluetooth it hangs and hangs and hangs. If I hit the enter key twice, I get a terminal logon. Once I logon, I can issue the startx command to boot into gnome. At that point, I get an error about... well I can't remember at the moment. The error doesn't have anything to do with bluez-util. I've been reading online and it seems that Ubuntu on HPs has some issues.

[sasanf (sasanforghani)]

Did some reading and changed name as follows:

Made sure that wireless was off by switching to off using hardware kill switch. When boot process got to Starting bluetooth, I hit enter. Logged on and then

cd /etc/rc2.d
sudo mv S25bluetooth s25bluetooth
sudo shutdown -r now

Turned wireless on with hardware kill switch. Ubuntu booted fine. I have to test wireless still.

Note: I had to install Ubuntu 8.04 beta 64 with the alt cd and I had to edit the boot command by hitting F6 and then removed the quiet and splash.

[sasanf (sasanforghani)]

I have to have my wireless card off when booting Ubuntu. If it is on at boot, the boot process hangs. If I have it off, then Ubuntu boots. Once booted, I can turn the wireless on using the hardware wireless switch. When the wireless is on at boot time, the boot process states something about USB at address and some number. I have pasted almost all the logs of the system. I hope the logs can help the developers in troubleshooting what the problem is. I may be wrong but I think the wireless/bluetooth are all somehow connected. I don't know how but it does seem that way.

daemonlog:

Apr 2 21:14:00 Travis-Ubuntu NetworkManager: <debug> [1207185240.573953] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_part3_size_5510937600').
Apr 2 21:14:00 Travis-Ubuntu NetworkManager: <debug> [1207185240.575200] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/volume_part3_size_5510937600').
Apr 2 21:14:00 Travis-Ubuntu NetworkManager: <debug> [1207185240.593118] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_part3_size_5510937600').
Apr 2 21:21:12 Travis-Ubuntu NetworkManager: <debug> [1207185672.659334] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/volume_part3_size_5510937600').
Apr 2 21:21:12 Travis-Ubuntu NetworkManager: <debug> [1207185672.716396] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_uuid_43a2389a_fae3_4611_9d05_106f86862c6a').
Apr 2 21:48:21 Travis-Ubuntu init: tty4 main process (5019) killed by TERM signal
Apr 2 21:48:21 Travis-Ubuntu init: tty5 main process (5020) killed by TERM signal
Apr 2 21:48:21 Travis-Ubuntu init: tty2 main process (5022) killed by TERM signal
Apr 2 21:48:21 Travis-Ubuntu init: tty3 main process (5024) killed by TERM signal
Apr 2 21:48:21 Travis-Ubuntu init: tty1 main process (5026) killed by TERM signal
Apr 2 21:48:21 Travis-Ubuntu init: tty6 main process (5027) killed by TERM signal
Apr 2 21:48:24 Travis-Ubuntu avahi-daemon[5491]: Got SIGTERM, quitting.
Apr 2 21:48:24 Travis-Ubuntu avahi-daemon[5491]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.10.108.
Apr 2 23:39:21 Travis-Ubuntu NetworkManager: <info> starting...
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: Found user 'avahi' (UID 108) and group 'avahi' (GID 119).
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: Successfully dropped root privileges.
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: avahi-daemon 0.6.22 starting up.
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: Successfully called chroot().
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: Successfully dropped remaining capabilities.
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: No service file found in /etc/avahi/services.
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: Network interface enumeration completed.
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: Registering HINFO record with values 'X86_64'/'LINUX'.
Apr 2 23:39:21 Travis-Ubuntu avahi-daemon[5498]: Server startup complete. Host name is Travis-Ubuntu.local. Local service c...

[sasanf (sasanforghani)]

As of Ubuntu 8.04 Beta AMD 64 daily build 04-04-2008, the bluetooth start script still hangs at boot time.

[Mike Mackintosh (mike-mackintosh)]

I can confirm this bug. Happens on dv9700z AMD Turion X2, Atheros AR5006eg/AR5007eg

Happens in both AMD64, and i386

[Thomas Hotz (thotz-deactivatedaccount)]

Can you reproduce this bug with a newer and supported Ubuntu version? Thank you!

[Launchpad Janitor (janitor)]

[Expired for bluez-utils (Ubuntu) because there has been no activity for 60 days.]