indicator-applet not turning off bluetooh (Lenovo x200s)

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

Bug Description

Binary package hint: bluez

1. Click on the bluetooth indicator-applet

2. Click on Turn Off Bluetooth
2. a. the bluetooth indicator light on my laptop still stays lite
2. b. previously during Lucid the light would go off

3. Click on Turn On Bluetooth
3. a. The light stays on again.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bluez 4.60-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
CheckboxSubmission: 728e74e7cabefd6ace4aa97ae53a1ff2
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Mon Apr 12 14:45:20 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: LENOVO 7465CTO
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=6886f363-9f1c-4c1d-99da-273344848f40 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 11/10/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET61WW (3.11 )
dmi.board.name: 7465CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET61WW(3.11):bd11/10/2009:svnLENOVO:pn7465CTO:pvrThinkPadX200s:rvnLENOVO:rn7465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7465CTO
dmi.product.version: ThinkPad X200s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0: Type: USB
  BD Address: 90:4C:E5:DB:C2:B6 ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:2026 acl:0 sco:0 events:69 errors:0
  TX bytes:2700 acl:0 sco:0 commands:69 errors:0

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :
tags: added: regression-potential
Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Works fine for me on my Lenovo T61.

The log reports this error:
bluetoothd[22286]: Can't init device hci0: Unknown error 132 (132)

Could you kill the bluetooth daemon and launch it manually with switches -n and -d and reproduce the error.
see if there is some information in the output.

Thanks

Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

I can't seem to figure out how to do that correctly, Baptiste. Could you list the steps I need to take.

tried:
killall bluetoothd
bluetoothd -n -d

And the only output was:
greg@zen:~$ bluetoothd -n -d
bluetoothd[3903]: Bluetooth daemon 4.60
bluetoothd[3903]: Enabling debug information
bluetoothd[3903]: parsing main.conf
bluetoothd[3903]: discovto=0
bluetoothd[3903]: pairto=0
bluetoothd[3903]: pageto=8192
bluetoothd[3903]: name=%h-%d
bluetoothd[3903]: class=0x000100
bluetoothd[3903]: discov_interval=0
bluetoothd[3903]: Key file does not have key 'DeviceID'
bluetoothd[3903]: Unable to get on D-Bus

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

hu, I forgot the sudo command before (as the bluetoothd needs to run as root).
so type "sudo bluetoothd -n -d"

and then post the output.

Thanks a lot.

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

Baptiste: As luck (?) would have it, the issue is now resolved with the latest kernel update (I just did an update today). So, the fix came in somewhere between 2.6.32-19.28-generic and 2.6.32-21-generic.

Thanks for your help, though.

Changed in bluez (Ubuntu):
status: Incomplete → Fix Released
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.