bluetooth not working

Bug #552579 reported by Sergey K
66
This bug affects 14 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: bluez

Hello!
bluetooth always turned off...
if i run bluetooth-properties and click "turn on blutooth" it stiil turned off.
This is bluetooth-properties output :
LANG=C;bluetooth-properties
** Message: adding killswitch idx 0 state 1
** Message: killswitch 0 is 1
** Message: killswitches state 1
** Message: RFKILL event: idx 0 type 2 op 2 soft 0 hard 0

** Message: killswitch 0 is 1
** Message: killswitches state 1

dmesg:
[94272.968369] usb 1-4.3: new full speed USB device using ehci_hcd and address 7
[94273.085046] usb 1-4.3: configuration #1 chosen from 1 choice
[94273.194824] gdm-session-wor[30096]: segfault at 11 ip 00000011 sp bfb0c7ac error 4 in libdbus-glib-1.so.2.1.0[110000+1c000]
[94273.577466] Bluetooth: Core ver 2.15
[94273.578764] NET: Registered protocol family 31
[94273.578768] Bluetooth: HCI device and connection manager initialized
[94273.578772] Bluetooth: HCI socket layer initialized
[94273.617626] Bluetooth: Generic Bluetooth USB driver ver 0.6
[94273.617884] usbcore: registered new interface driver btusb
[94273.963265] Bluetooth: L2CAP ver 2.14
[94273.963270] Bluetooth: L2CAP socket layer initialized
[94274.064640] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[94274.064644] Bluetooth: BNEP filters: protocol multicast
[94274.128909] Bridge firewalling registered
[94274.359439] Bluetooth: SCO (Voice Link) ver 0.6
[94274.359449] Bluetooth: SCO socket layer initialized
[94274.620039] Bluetooth: RFCOMM TTY layer initialized
[94274.620046] Bluetooth: RFCOMM socket layer initialized
[94274.620048] Bluetooth: RFCOMM ver 1.11

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bluez 4.60-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
Date: Wed Mar 31 18:50:01 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: Acer, inc. Aspire 1640Z
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-18-generic root=UUID=a44ec12f-0f3e-4c45-b386-0f04e9ab23a2 ro quiet splash
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 02/21/06
dmi.bios.vendor: Acer
dmi.bios.version: 3A18
dmi.board.name: Lugano3
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: , Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvr3A18:bd02/21/06:svnAcer,inc.:pnAspire1640Z:pvrNotApplicable:rvnAcer,Inc.:rnLugano3:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 1640Z
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.
hciconfig:
 hci0: Type: USB
  BD Address: 00:10:60:A4:AC:F2 ACL MTU: 192:8 SCO MTU: 64:8
  UP RUNNING PSCAN
  RX bytes:2388 acl:0 sco:0 events:78 errors:0
  TX bytes:311 acl:0 sco:0 commands:78 errors:0
rfkill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

Revision history for this message
Sergey K (koblin) wrote :
Sergey K (koblin)
summary: - [lucid] blutooth not working
+ [lucid] bluetooth not working
Revision history for this message
Jonathan Harker (jonathanharker) wrote : Re: [lucid] bluetooth not working

dpkg -l |grep blue
ii bluez 4.60-0ubuntu7 Bluetooth tools and daemons
ii bluez-alsa 4.60-0ubuntu7 Bluetooth audio support
ii bluez-cups 4.60-0ubuntu7 Bluetooth printer driver for CUPS
ii bluez-gstreamer 4.60-0ubuntu7 Bluetooth GStreamer support
ii gnome-bluetooth 2.30.0-0ubuntu2 GNOME Bluetooth tools
ii libbluetooth3 4.60-0ubuntu7 Library to use the BlueZ Linux Bluetooth sta
ii libgnome-bluetooth7 2.30.0-0ubuntu2 GNOME Bluetooth tools - support library
ii pulseaudio-module-bluetooth 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 Bluetooth module for PulseAudio sound server

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

Jonathan,

what is the purpose of just pasting the list of bluez package?
If you have a bug with bluetooth, please open a new bug where you state what your problem is.
to open a bug, open a terminal and type "ubuntu-bug bluez"

Thanks.

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

Hi Sergey,

So You're are postive you can do all operations in terminal (using tools in /usr/share/doc/bluez/examples/ but not with gnome-bluetooth graphical interface?
there is no improvement, is the bug still here?

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

By the way, does few:
hciconfig reset or
hciconfig down && hciconfig up solve the problem?

Changed in bluez (Ubuntu):
status: New → Triaged
affects: bluez (Ubuntu) → gnome-bluetooth (Ubuntu)
Revision history for this message
Sergey K (koblin) wrote :

Hi!
Yes, bug still here.
hciconfig down && hciconfig don't solve problem...

all tools in /usr/share/doc/bluez/examples/ crash with something like this:
./test-device
Traceback (most recent call last):
  File "./test-device", line 9, in <module> manager = dbus.Interface(bus.get_object("org.bluez", "/"), "org.bluez.Manager")
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 244, in get_object follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 241, in __init__ self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 183, in activate_name_owner self.start_service_by_name(bus_name)
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 281, in start_service_by_name 'su', (bus_name, flags)))
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files

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

hmm,

it looks like there is a problem somewhere:
- is there a file /etc/dbus-1/system.d/bluetooth.conf ?
- Are you sure the bluetooth deamon is started (as root)?

Thanks.

Revision history for this message
Sergey K (koblin) wrote :

/etc/dbus-1/system.d/bluetooth.conf exist

$ ps aux| grep bluetooth
sergeyk 1583 0.0 0.2 20076 4596 ? S Apr17 0:00 bluetooth-applet
root 16176 0.0 0.0 0 0 ? S 15:52 0:00 [bluetooth]
root 16650 0.0 0.0 4048 1304 ? S<s 16:07 0:00 /usr/sbin/bluetoothd --udev

i'm restarting /etc/init/d/bluetooth as root several times, but nothing hapend

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

Hi again,

Could you, as root kill the bluetoothd daemon, and launch it as root with the options -n -d and tell me if there is any error.
Could install d-feet, and see if you can see the dbus interface of bluez (org.bluez), in the "system bus" tab.

thanks.

Revision history for this message
Sergey K (koblin) wrote :
Download full text (8.0 KiB)

no, i don't see org.bluez (screenshot attached)

# bluetoothd -n -d
bluetoothd[20197]: Bluetooth daemon 4.60
bluetoothd[20197]: Enabling debug information
bluetoothd[20197]: parsing main.conf
bluetoothd[20197]: discovto=0
bluetoothd[20197]: pairto=0
bluetoothd[20197]: pageto=8192
bluetoothd[20197]: name=%h-%d
bluetoothd[20197]: class=0x000100
bluetoothd[20197]: discov_interval=0
bluetoothd[20197]: Key file does not have key 'DeviceID'
bluetoothd[20197]: Starting SDP server
bluetoothd[20197]: Loading builtin plugins
bluetoothd[20197]: Loading audio plugin
bluetoothd[20197]: Loading input plugin
bluetoothd[20197]: Loading serial plugin
bluetoothd[20197]: Loading network plugin
bluetoothd[20197]: Loading service plugin
bluetoothd[20197]: Loading hciops plugin
bluetoothd[20197]: Loading storage plugin
bluetoothd[20197]: Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[20197]: Loading netlink plugin
bluetoothd[20197]: register_interface: path /org/bluez/20197/any
bluetoothd[20197]: Registered interface org.bluez.Service on path /org/bluez/20197/any
bluetoothd[20197]: Starting experimental netlink support
bluetoothd[20197]: Failed to find Bluetooth netlink family
bluetoothd[20197]: Failed to init netlink plugin
bluetoothd[20197]: /etc/bluetooth/network.conf: Key file does not have key 'Disable'
bluetoothd[20197]: /etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[20197]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[20197]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[20197]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[20197]: Config options: InterfacePrefix=bnep%d, PANU_Script=(null), GN_Script=(null), NAP_Script=(null), GN_Interface=pan0, NAP_Interface=pan1, Security=true
bluetoothd[20197]: bridge pan0 created
bluetoothd[20197]: input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[20197]: Unix socket created: 9
bluetoothd[20197]: audio.conf: Key file does not have key 'AutoConnect'
bluetoothd[20197]: Telephony plugin initialized
bluetoothd[20197]: HFP AG features: "Ability to reject a call" "Enhanced call status" "Extended Error Result Codes"
bluetoothd[20197]: HCI dev 0 registered
bluetoothd[20197]: child 20200 forked
bluetoothd[20197]: btd_adapter_ref(0x210e6068): ref=1
bluetoothd[20197]: HCI dev 0 up
bluetoothd[20197]: Starting security manager 0
bluetoothd[20197]: Stopping Inquiry at adapter startup
bluetoothd[20197]: register_interface: path /org/bluez/20197/hci0
bluetoothd[20197]: Registered interface org.bluez.Service on path /org/bluez/20197/hci0
bluetoothd[20197]: network_server_probe: path /org/bluez/20197/hci0
bluetoothd[20197]: btd_adapter_ref(0x210e6068): ref=2
bluetoothd[20197]: Adding record with handle 0x10000
bluetoothd[20197]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[20197]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[20197]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[20197]: Record pattern UUID 00001115-0000-1000-8000-00805f9
bluetoothd[20197]: register_server_record: got record id 0x10000
bluetoothd[20197]: Registere...

Read more...

affects: gnome-bluetooth (Ubuntu) → bluez (Ubuntu)
Changed in bluez (Ubuntu):
importance: Undecided → Low
Revision history for this message
Sindhu S (sindhu-s) wrote :

Mine is here...

➜ default sudo bluetoothd -nd
bluetoothd[5740]: Bluetooth daemon 4.61
bluetoothd[5740]: Enabling debug information
bluetoothd[5740]: parsing main.conf
bluetoothd[5740]: discovto=0
bluetoothd[5740]: pairto=0
bluetoothd[5740]: pageto=8192
bluetoothd[5740]: name=%h-%d
bluetoothd[5740]: class=0x000100
bluetoothd[5740]: discov_interval=0
bluetoothd[5740]: Key file does not have key 'DeviceID'
bluetoothd[5740]: Starting SDP server
bluetoothd[5740]: Loading builtin plugins
bluetoothd[5740]: Loading audio plugin
bluetoothd[5740]: Loading input plugin
bluetoothd[5740]: Loading serial plugin
bluetoothd[5740]: Loading network plugin
bluetoothd[5740]: Loading service plugin
bluetoothd[5740]: Loading hciops plugin
bluetoothd[5740]: Loading hal plugin
bluetoothd[5740]: Loading storage plugin
bluetoothd[5740]: Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[5740]: Loading netlink plugin
bluetoothd[5740]: register_interface: path /org/bluez/5740/any
bluetoothd[5740]: Registered interface org.bluez.Service on path /org/bluez/5740/any
bluetoothd[5740]: Starting experimental netlink support
bluetoothd[5740]: Failed to find Bluetooth netlink family
bluetoothd[5740]: Failed to init netlink plugin
bluetoothd[5740]: /etc/bluetooth/network.conf: Key file does not have key 'Disable'
bluetoothd[5740]: /etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[5740]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[5740]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[5740]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[5740]: Config options: InterfacePrefix=bnep%d, PANU_Script=(null), GN_Script=(null), NAP_Script=(null), GN_Interface=pan0, NAP_Interface=pan1, Security=true
bluetoothd[5740]: bridge pan0 created
bluetoothd[5740]: input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[5740]: Unix socket created: 9
bluetoothd[5740]: audio.conf: Key file does not have key 'AutoConnect'
bluetoothd[5740]: Telephony plugin initialized
bluetoothd[5740]: HFP AG features: "Ability to reject a call" "Enhanced call status" "Extended Error Result Codes"
bluetoothd[5740]: Entering main loop
bluetoothd[5740]: RFKILL event idx 0 type 1 op 0 soft 0 hard 0
bluetoothd[5740]: RFKILL event idx 1 type 2 op 0 soft 0 hard 0

Revision history for this message
Sindhu S (sindhu-s) wrote :

Funny that when I start the daemon with sudo bluetooth -nd blueman-manager applet runs fine otherwise, bluetooth doesn't work.

Revision history for this message
Jens Janssen (jayjay) wrote :

Sometimes I have the same problem. Bluetooth simply doesn't come up. The Icon in the panel is greyed out and I'm not able to turn it on back again. I think the problem is udev rule "97-bluetooth.rules" that doesn't work. You can try to run manually "/usr/sbin/bluetoothd --udev".

Revision history for this message
Jens Janssen (jayjay) wrote :

Problem solved for me at least:
I changed the content of /lib/udev/rules.d/97-bluetooth.rules
from
ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/sbin/bluetoothd --udev"
to
ACTION=="add", SUBSYSTEM=="bluetooth", KERNELS=="hci0", RUN+="/usr/sbin/bluetoothd --udev"
(change hci0 corresponding to your device name)

This fix needs some testing. If it solve your problem - OK. Otherwise I have to open a new bugreport.

Revision history for this message
Sergey K (koblin) wrote :

manipulations witch 97-bluetooth.rules not solve my problem... issue still here :-\

Revision history for this message
Jens Janssen (jayjay) wrote :

...you're right. The problem occurs occasionally, but less often (for me). Did someone ever tried

sudo /usr/sbin/bluetoothd --udev

after bluetooth doesn't come up? If this works than udev or bluetoothd has some timing problems.

Revision history for this message
seaice amir (bitkeep) wrote :

I tried sudo /usr/sbin/bluetoothd --udev several times, until now, it worked only once.

papukaija (papukaija)
summary: - [lucid] bluetooth not working
+ bluetooth not working
Revision history for this message
Ruslan (b7-10110111) wrote :

It also appears on my EEEPC 901 on Ubuntu 11.04 and development Oneiric.
Restarting bluetoothd does work around this problem. Well, at least after bluetoothd restart, "hcitool dev" begins to report existence of my onboard adapter.

Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.

Changed in bluez (Ubuntu):
status: Triaged → Invalid
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.