/etc/init.d/bluetooth does not restart

Bug #359929 reported by ecukalla
2
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: bluetooth

Hi all,

$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
$ apt-cache policy bluetooth
bluetooth:
  Installed: 4.32-0ubuntu4
  Candidate: 4.32-0ubuntu4
  Version table:
 *** 4.32-0ubuntu4 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

I notice that when I try to restart /etc/init.d/bluetooth the bluetooth service is not enalbed always. The sequence of is like this;
ones it stop-start successfully
ones it doesn't.
ones it stop-start successfully
ones it doesn't.

Here are the logs from my system:

# /etc/init.d/bluetooth restart
 * Stopping bluetooth [ OK ]
 * Starting bluetooth [ OK ]
# /etc/init.d/bluetooth restart
 * Stopping bluetooth [ OK ]
 * Starting bluetooth [ OK ]
# /etc/init.d/bluetooth restart
 * Stopping bluetooth [ OK ]
 * Starting bluetooth [ OK ]
# /etc/init.d/bluetooth restart
 * Stopping bluetooth [ OK ]
 * Starting bluetooth [ OK ]
#

While I was restarting bluetooth i hade another terminal tailing the syslog:

$ tail -f /var/log/syslog
Apr 12 01:42:45 fujis bluetoothd[7733]: Unregistered interface org.bluez.NetworkPeer on path /org/bluez/7733/hci0
Apr 12 01:42:45 fujis bluetoothd[7733]: Unregistered interface org.bluez.NetworkHub on path /org/bluez/7733/hci0
Apr 12 01:42:45 fujis bluetoothd[7733]: Unregistered interface org.bluez.NetworkRouter on path /org/bluez/7733/hci0
Apr 12 01:42:45 fujis bluetoothd[7733]: Unregistered interface org.bluez.Serial on path /org/bluez/7733/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:42:45 fujis bluetoothd[7733]: Unregistered interface org.bluez.Control on path /org/bluez/7733/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:42:46 fujis bluetoothd[7733]: bridge pan0 removed
Apr 12 01:42:46 fujis bluetoothd[7733]: Stopping SDP server
Apr 12 01:42:46 fujis bluetoothd[7733]: Exit

Apr 12 01:42:59 fujis bluetoothd[7821]: Bluetooth daemon
Apr 12 01:42:59 fujis bluetoothd[7821]: Starting SDP server
Apr 12 01:42:59 fujis bluetoothd[7821]: Starting experimental netlink support
Apr 12 01:42:59 fujis bluetoothd[7821]: Failed to find Bluetooth netlink family
Apr 12 01:42:59 fujis bluetoothd[7821]: bridge pan0 created
Apr 12 01:42:59 fujis bluetoothd[7821]: Registered interface org.bluez.Service on path /org/bluez/7821/any
Apr 12 01:42:59 fujis bluetoothd[7821]: HCI dev 0 registered
Apr 12 01:42:59 fujis bluetoothd[7821]: HCI dev 0 up
Apr 12 01:42:59 fujis bluetoothd[7821]: Starting security manager 0
Apr 12 01:42:59 fujis bluetoothd[7821]: Registered interface org.bluez.NetworkPeer on path /org/bluez/7821/hci0
Apr 12 01:42:59 fujis bluetoothd[7821]: Registered interface org.bluez.NetworkHub on path /org/bluez/7821/hci0
Apr 12 01:42:59 fujis bluetoothd[7821]: Registered interface org.bluez.NetworkRouter on path /org/bluez/7821/hci0
Apr 12 01:42:59 fujis bluetoothd[7821]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/7821/hci0
Apr 12 01:42:59 fujis bluetoothd[7821]: Registered interface org.bluez.Service on path /org/bluez/7821/hci0
Apr 12 01:42:59 fujis bluetoothd[7821]: probe failed with driver input-headset for device /org/bluez/7821/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:42:59 fujis bluetoothd[7821]: Registered interface org.bluez.Serial on path /org/bluez/7821/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:42:59 fujis bluetoothd[7821]: Registered interface org.bluez.Control on path /org/bluez/7821/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:42:59 fujis bluetoothd[7821]: Adapter /org/bluez/7821/hci0 has been enabled

Apr 12 01:43:10 fujis bluetoothd[7821]: Unregistered interface org.bluez.NetworkPeer on path /org/bluez/7821/hci0
Apr 12 01:43:10 fujis bluetoothd[7821]: Unregistered interface org.bluez.NetworkHub on path /org/bluez/7821/hci0
Apr 12 01:43:10 fujis bluetoothd[7821]: Unregistered interface org.bluez.NetworkRouter on path /org/bluez/7821/hci0
Apr 12 01:43:10 fujis bluetoothd[7821]: Unregistered interface org.bluez.Serial on path /org/bluez/7821/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:43:10 fujis bluetoothd[7821]: Unregistered interface org.bluez.Control on path /org/bluez/7821/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:43:10 fujis bluetoothd[7821]: bridge pan0 removed
Apr 12 01:43:10 fujis bluetoothd[7821]: Stopping SDP server
Apr 12 01:43:10 fujis bluetoothd[7821]: Exit

Apr 12 01:43:16 fujis bluetoothd[7903]: Bluetooth daemon
Apr 12 01:43:16 fujis bluetoothd[7903]: Starting SDP server
Apr 12 01:43:16 fujis bluetoothd[7903]: Starting experimental netlink support
Apr 12 01:43:16 fujis bluetoothd[7903]: Failed to find Bluetooth netlink family
Apr 12 01:43:16 fujis bluetoothd[7903]: bridge pan0 created
Apr 12 01:43:16 fujis bluetoothd[7903]: Registered interface org.bluez.Service on path /org/bluez/7903/any
Apr 12 01:43:16 fujis bluetoothd[7903]: HCI dev 0 registered
Apr 12 01:43:16 fujis bluetoothd[7903]: HCI dev 0 up
Apr 12 01:43:16 fujis bluetoothd[7903]: Starting security manager 0
Apr 12 01:43:17 fujis bluetoothd[7903]: Registered interface org.bluez.NetworkPeer on path /org/bluez/7903/hci0
Apr 12 01:43:17 fujis bluetoothd[7903]: Registered interface org.bluez.NetworkHub on path /org/bluez/7903/hci0
Apr 12 01:43:17 fujis bluetoothd[7903]: Registered interface org.bluez.NetworkRouter on path /org/bluez/7903/hci0
Apr 12 01:43:17 fujis bluetoothd[7903]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/7903/hci0
Apr 12 01:43:17 fujis bluetoothd[7903]: Registered interface org.bluez.Service on path /org/bluez/7903/hci0
Apr 12 01:43:17 fujis bluetoothd[7903]: probe failed with driver input-headset for device /org/bluez/7903/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:43:17 fujis bluetoothd[7903]: Registered interface org.bluez.Serial on path /org/bluez/7903/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:43:17 fujis bluetoothd[7903]: Registered interface org.bluez.Control on path /org/bluez/7903/hci0/dev_00_22_FD_0A_91_BE
Apr 12 01:43:17 fujis bluetoothd[7903]: Adapter /org/bluez/7903/hci0 has been enabled

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Sorry, but I don't see any error in the bluetooth log, what is the problem you're experiencing (I'm certainly blind).
So could you try to launch bluetoothd with debug to have more verbosity, and set a marker in the bluetooth log each where you did a restart?

Thanks

Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Mario Limonciello (superm1) wrote :

The behavior of the init script has changed for Ubuntu 9.10. It now uses pkill to stop the process and udev will restart it for you.

Changed in bluez (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Pearl (pearl-selvan) wrote :

Even I have tried to restart , but its nit staring .

clicked , System --> Preference --> Bluetooth Manager"

But I am getting the error message "Connection to Bluez failed " ., Bluez daemon is not running , blue manager cannot continue .
(Please find the attachment )
I am using ubuntu 9.10
pearl@pearl-laptop:~/myS$ uname -a
Linux pearl-laptop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

Please help me and solve my mobile (sony ericession c510 model connect to laptop )

Thanks ,
MuthuSR

Revision history for this message
BryanFRitt (bryanfritt) wrote :

"Connection to BlueZ failed"
Reinstalling 'BlueZ' in synaptic fixed it for me

What caused it to go bad?, or what went wrong?, What did reinstalling BlueZ change?, I don't know, but reinstalling BlueZ fixed the problem (or at least seamed to fix it, this time).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.