Bluetooth can't be turned off correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bluez
I meet a problem that I can't turn off Bluetooth correctly on ARM platform with Ubuntu Lucid.
If the bluetooth device is under "UP RUNNING PSCAN ISCAN" mode, I have to run "hciconfig hci0 down" twice to turn off it. Following is the state information:
[LOG]
root@ubuntu-
hci0: Type: SDIO
BD Address: 00:24:23:10:97:A3 ACL MTU: 1021:7 SCO MTU: 240:3
UP RUNNING PSCAN ISCAN
RX bytes:2324 acl:0 sco:0 events:71 errors:0
TX bytes:2746 acl:0 sco:0 commands:71 errors:0
root@ubuntu-
root@ubuntu-
hci0: Type: SDIO
BD Address: 00:24:23:10:97:A3 ACL MTU: 1021:7 SCO MTU: 240:3
UP RUNNING PSCAN
RX bytes:3467 acl:0 sco:0 events:105 errors:0
TX bytes:4227 acl:0 sco:0 commands:105 errors:0
root@ubuntu-
root@ubuntu-
hci0: Type: SDIO
BD Address: 00:24:23:10:97:A3 ACL MTU: 1021:7 SCO MTU: 240:3
DOWN
RX bytes:3477 acl:0 sco:0 events:106 errors:0
TX bytes:4234 acl:0 sco:0 commands:106 errors:0
[/LOG]
At first time, it changes the mode from visible to invisible. Then at second time, it goes to off mode. It's not reasonable. I have try it on Ubuntu Karmic, it works normarlly. (From "UP RUNNING PSCAN ISCAN" to "DOWN" mode directly with command "hciconfig hci0 down")
The release of Ubuntu that I use is Ubuntu Lucid.
root@
Description: Ubuntu lucid (development branch)
Release: 10.04
And the bluez version is 4.60-0ubuntu5.
This is part of the /var/log/syslog:
[LOG]
Jul 29 08:54:01 ubuntu-laptop bluetoothd[1061]: Bluetooth daemon 4.60
Jul 29 08:54:01 ubuntu-laptop bluetoothd[1062]: Starting SDP server
Jul 29 08:54:01 ubuntu-laptop bluetoothd[1062]: Starting experimental netlink support
Jul 29 08:54:01 ubuntu-laptop bluetoothd[1062]: Failed to find Bluetooth netlink family
Jul 29 08:54:01 ubuntu-laptop bluetoothd[1062]: Failed to init netlink plugin
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: Can't create GN bridge
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: Unable to start SCO server socket
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: Failed to init audio plugin
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: HCI dev 0 registered
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: Failed to open RFKILL control device
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: accept: Socket operation on non-socket (88)
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: HCI dev 0 up <------- initialize
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: Starting security manager 0
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: Parsing /etc/bluetooth/
Jul 29 08:54:02 ubuntu-laptop bluetoothd[1062]: Adapter /org/bluez/
Jul 29 08:54:15 ubuntu-laptop AptDaemon: INFO: Initializing daemon
Jul 29 08:54:33 ubuntu-laptop bluetoothd[1062]: HCI dev 0 down
Jul 29 08:54:33 ubuntu-laptop bluetoothd[1062]: Adapter /org/bluez/
Jul 29 08:54:33 ubuntu-laptop bluetoothd[1062]: Stopping security manager 0
Jul 29 08:54:33 ubuntu-laptop bluetoothd[1062]: HCI dev 0 up
Jul 29 08:54:33 ubuntu-laptop bluetoothd[1062]: Starting security manager 0
Jul 29 08:54:33 ubuntu-laptop bluetoothd[1062]: Adapter /org/bluez/
Jul 29 08:59:16 ubuntu-laptop AptDaemon: INFO: Quiting due to inactivity
Jul 29 08:59:16 ubuntu-laptop AptDaemon: INFO: Shutdown was requested
Jul 29 09:06:29 ubuntu-laptop bluetoothd[1062]: HCI dev 0 down
Jul 29 09:06:29 ubuntu-laptop bluetoothd[1062]: Adapter /org/bluez/
Jul 29 09:06:29 ubuntu-laptop bluetoothd[1062]: Stopping security manager 0
Jul 29 09:06:29 ubuntu-laptop bluetoothd[1062]: HCI dev 0 up
Jul 29 09:06:29 ubuntu-laptop bluetoothd[1062]: Starting security manager 0
Jul 29 09:06:29 ubuntu-laptop bluetoothd[1062]: Adapter /org/bluez/
Jul 29 09:06:41 ubuntu-laptop bluetoothd[1062]: HCI dev 0 down
Jul 29 09:06:41 ubuntu-laptop bluetoothd[1062]: Adapter /org/bluez/
Jul 29 09:06:41 ubuntu-laptop bluetoothd[1062]: Stopping security manager 0
[/LOG]
tags: | added: lucid |
summary: |
- Bluetooth can't be turned off correctly on Lucid + Bluetooth can't be turned off correctly |
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.