Bug#525220:

[Dominique Meeùs <dominique@d-meeus.be>]

Maximi89 a écrit ce qui suit, le 03/05/09 21:47 :
> maximi89@Maximiliano:~$ sudo dpkg -l | grep bluez : ii bluez 
> 4.35-0ubuntu1 
I wrote this on one line to keep the message shorter. After : ii etc. is 
the result. You have to understand it as
sudo dpkg -l | grep bluez
   ii    bluez        4.35-0ubuntu1
> maximi89@Maximiliano:~$ sudo /etc/init.d/bluetooth stop
> Stopping bluetooth: hcid.  
> ...
> maximi89@Maximiliano:~$ sudo hciconfig -a
> hci0: Type: USB  
>   BD Address: 00:11:67:CB:5D:87 ACL MTU: 1021:4 SCO MTU: 48:10
>   UP RUNNING PSCAN ISCAN  
>   RX bytes:1226 acl:0 sco:0 events:26 errors:0  
>   TX bytes:347 acl:0 sco:0 commands:27 errors:0  
>   Features: 0xff 0xfe 0xff 0x7e 0x98 0x19 0x00 0x80  
>   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3  
>   Link policy: RSWITCH HOLD SNIFF PARK  
>   Link mode: SLAVE ACCEPT  
>   Name: 'Maximiliano-0'  
>   Class: 0x080104  
>   Service Classes: Capturing  
>   Device Class: Computer, Desktop workstation  
>   HCI Ver: 2.0 (0x3) HCI Rev: 0x302 LMP Ver: 2.0 (0x3) LMP Subver: 0x302
>   Manufacturer: Integrated System Solution Corp. (57) 
In your case too, there is no more "hci0 command tx timeout" with 
bluetooth stopped.

This should be an important information to debug this problem. I am not 
able to do it myself, so the next step should be to convince some 
developer to take the problem seriously