[sound-nua] Bluetooth device not listed if change mode to Off
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
Medium
|
James M. Leddy | ||
Precise |
Fix Released
|
Medium
|
James M. Leddy | ||
gnome-control-center |
Fix Released
|
Medium
|
|||
gnome-control-center (Ubuntu) |
Fix Released
|
Low
|
David Henningsson | ||
Precise |
Fix Released
|
Low
|
Unassigned |
Bug Description
* Impact: users can turn off bluetooth devices without being able to turn them back on
* Test Case:
- connect a bluetooth audio device (headset for example)
- go to system settings -> sound (under Unity)
- look at the profiles for the bluetooth device
"off" shouldn't be listed
* Regression potential:
limited, check that other profiles are listed are they should
-----
I've accidentally changed the operation mode of my Bluetooth phone from A2DP to Off, then the device is removed from the list.
Instead, it should be marked as disabled, and kept on list, so I could reactivate it later.
To reactivate, I needed to install tdbtools, open tdb file that store this settings (pulseaudio), then remove my device from records. After that, the device was listed again on Sound Settings as A2DP sound output.
Changed in gnome-control-center (Ubuntu): | |
importance: | Undecided → Low |
Changed in oem-priority: | |
importance: | Undecided → Medium |
Changed in gnome-control-center (Ubuntu): | |
assignee: | nobody → David Henningsson (diwic) |
Changed in oem-priority: | |
assignee: | nobody → James M. Leddy (jm-leddy) |
tags: | added: rls-r-incoming |
Changed in gnome-control-center (Ubuntu Precise): | |
importance: | Undecided → Low |
Changed in gnome-control-center (Ubuntu): | |
status: | New → In Progress |
Changed in gnome-control-center (Ubuntu Precise): | |
status: | New → In Progress |
Changed in gnome-control-center (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in gnome-control-center (Ubuntu Precise): | |
status: | In Progress → Fix Committed |
description: | updated |
Changed in oem-priority: | |
status: | New → Fix Committed |
Changed in gnome-control-center: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in gnome-control-center (Ubuntu Precise): | |
status: | Fix Committed → In Progress |
Changed in oem-priority: | |
status: | Fix Committed → In Progress |
Changed in oem-priority: | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
Changed in gnome-control-center: | |
status: | New → Fix Released |
Changed in oem-priority: | |
status: | Fix Committed → Fix Released |
I want to fix this for 13.04 / Gnome 3.8.
Anyway, should this happen again, it's easier to fix from the pavucontrol application than tdbtools.