toggling bluez adapter's Powered is unreliable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
powering down an adapter times out, and powering it back up again doesn't seem to work at all.
Demonstration with bluez-test-adapter after a cold boot:
---
charles@sita:~$ bluez-test-adapter powered
1
charles@sita:~$ bluez-test-adapter powered off
Traceback (most recent call last):
File "/usr/bin/
adapter.
File "/usr/lib/
return self._proxy_
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
charles@sita:~$ bluez-test-adapter powered
0
charles@sita:~$ bluez-test-adapter powered on
charles@sita:~$ bluez-test-adapter powered
0
charles@sita:~$ bluez-test-adapter list
[ /org/bluez/793/hci0 ]
Name = ubuntu-0
Powered = 0
Devices = dbus.Array(
Discoverabl
PairableTimeout = 0
Discoverable = 0
Address = 60:D8:19:AA:F3:8B
Discovering = 0
Pairable = 1
Class = 0x000000
UUIDs = dbus.Array(
charles@sita:~$ dpkg -s bluez
Package: bluez
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 2375
Maintainer: Ubuntu Developers <email address hidden>
Architecture: i386
Multi-Arch: foreign
Version: 4.101-0ubuntu8b1
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.