Bluetooth doesn't work in 9.10 (x86-64)

Bug #543674 reported by Emanem
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: bluez

Hi,

while Bluetooth on the same hardware has worked since my first install of Ubuntu (7.10), apparently now it doesn't work anymore.
If I install blueman, when I right click on the greyed icon and choos "Turn Bluetooth On", it doesn't work.

Cheers,

----------------
bluez:
  Installed: 4.51-0ubuntu2
  Candidate: 4.51-0ubuntu2
  Version table:
 *** 4.51-0ubuntu2 0
        500 http://gb.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: amd64
Date: Sun Mar 21 19:58:23 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: bluez 4.51-0ubuntu2
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: bluez
Uname: Linux 2.6.31-20-generic x86_64

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

Hi there,

please could you run the following commands and post the results here.
$ lsusb |grep blue -i
$ lsmod |grep bt
$ grep -i blue /var/log/dmesg
$ hciconfig
$ rfkill list
# perhaps you'll need to install getfacl
$ getfacl /dev/rfkill

thanks

Revision history for this message
Emanem (emaentra) wrote :

Here they are:
lsusb |grep blue -i
Bus 004 Device 002: ID 0b05:1712 ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR adapter

lsmod |grep bt
btusb 14260 0

grep -i blue /var/log/dmesg
[ 0.390006] Bluetooth: Core ver 2.15
[ 0.390020] Bluetooth: HCI device and connection manager initialized
[ 0.390020] Bluetooth: HCI socket layer initialized
[ 3.645787] Bluetooth: L2CAP ver 2.13
[ 3.645789] Bluetooth: L2CAP socket layer initialized
[ 3.645792] Bluetooth: SCO (Voice Link) ver 0.6
[ 3.645794] Bluetooth: SCO socket layer initialized
[ 3.645820] Bluetooth: RFCOMM TTY layer initialized
[ 3.645822] Bluetooth: RFCOMM socket layer initialized
[ 3.645824] Bluetooth: RFCOMM ver 1.11
[ 32.321265] Bluetooth: Generic Bluetooth USB driver ver 0.5

hciconfig
hci0: Type: USB
 BD Address: 00:1D:60:4D:25:B2 ACL MTU: 384:8 SCO MTU: 64:8
 DOWN
 RX bytes:688 acl:0 sco:0 events:23 errors:0
 TX bytes:91 acl:0 sco:0 commands:23 errors:1

rfkill list
0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

getfacl: Removing leading '/' from absolute path names
# file: dev/rfkill
# owner: root
# group: root
user::rw-
group::r--
other::r--

Cheers,

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

Hi there,

Could you run the command 'sudo hciconfig hci0 up' and do 'sudo hciconfig hci0' afterward?

thanks

Revision history for this message
Emanem (emaentra) wrote :

Here is it the output:
hci0: Type: USB
 BD Address: 00:1D:60:4D:25:B2 ACL MTU: 384:8 SCO MTU: 64:8
 UP RUNNING PSCAN ISCAN
 RX bytes:1651 acl:0 sco:0 events:50 errors:0
 TX bytes:704 acl:0 sco:0 commands:50 errors:0

Cheers,

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

So now what is the situation, is it working better?

Revision history for this message
Emanem (emaentra) wrote :

Now it works beautifully.
What was the issue btw?

Thanks again,

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

Hi there.

hciconfig showed the adapter was down

hciconfig
hci0: Type: USB
 BD Address: 00:1D:60:4D:25:B2 ACL MTU: 384:8 SCO MTU: 64:8
 DOWN
 ^^^^

The command "sudo hciconfig hci0 up" fixed that.
I'm happy this is fixed.

Regards.

Changed in bluez (Ubuntu):
status: New → Fix Released
Revision history for this message
Emanem (emaentra) wrote :

Just FYI, when I right click on blueman and then turnoff, I can't do turn on anymore (or even the "sudo hciconfig hci0 up") unless I reboot.
Cheer,

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

Perhaps there is also a blug in blueman (which I don't use myself) ?
Have you tried with gnome-bluetooth?

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.