[sound-nua] Bluetooth device not listed if change mode to Off

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.

There's something I can do to help fixing it in 12.10? I've just installed it here :)

Thanks for your assistance. To be honest, I'm a little surprised that it happened. Did it disappear on both input and output tabs? If it's still around on the other tab, maybe you can use that tab to work around the bug and switch profile there.

Yes, disappears on both tabs. Is like I had disconnected it. I'm attaching two screenshots with the phone connected and after switching profile to "Off".

BTW, thanks for the pavucontrol tip! I'd never remember of this workaround :)

Cheers

I can replicate this under both 12.04 and 12.10.

Quick fix (untested) : http://bazaar.launchpad.net/~diwic/gnome-control-center/remove-off-profile/revision/471

Quick fix tested and working in 12.04.

Tried upstreaming this to gnome, but bugzilla.gnome.org seems down. Will try again later.

https://bugzilla.gnome.org/show_bug.cgi?id=693654

This bug was fixed in the package gnome-control-center - 1:3.6.3-0ubuntu13

---------------
gnome-control-center (1:3.6.3-0ubuntu13) raring; urgency=low

  * debian/patches/sound_nua_panel.patch:
    - don't allow to turn bluetooth devices off, or they are dropped from
      the devices list and there is no way to turn them back on,
      thanks David Henningsson (lp: #1071561)
 -- Sebastien Bacher <email address hidden> Tue, 12 Feb 2013 10:47:59 +0100

Hello Jimmy, or anyone else affected,

Accepted gnome-control-center into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome-control-center/1:3.4.2-0ubuntu0.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Could a SRU team member reject the upload? It creates https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1136216

The sound capplet fails to load with those errors:
/usr/lib/control-center-1/panels/libsoundnua.so: undefined symbol: gvc_mixer_ui_device_is_output

Not sure why that just started to happening in that version, there is nothing in the diff that should makes a difference on the symbols/linking and diffing the build logs from 0.9 and 0.10 there is this new line

"dpkg-shlibdeps: warning: debian/gnome-control-center/usr/lib/control-center-1/panels/libsoundnua.so contains an unresolvable reference to symbol gvc_mixer_ui_device_is_output: it's probably a plugin."

but nothing in the linker flags changed...

ok, I found the issue, the diff is buggy, extra lines got added to a new file but the offset of the patch didn't get update which did lead to have the end of file truncated... note for next time: don't try to be too smart about reducing the diff for easier review

I've uploaded a 0ubuntu11 that fixes the bug

Hello Jimmy, or anyone else affected,

Accepted gnome-control-center into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome-control-center/1:3.4.2-0ubuntu0.11 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello guys 'n gals!

I'm using quantal over here. There's a .0ubuntu19.1 quantal-proposed package to download here, but nothing's changed, so I can't test yet. I'm waiting for a commit to quantal, and as soon as it's available, I'll check it :D

Cheers

Hi Kent,

Would you please test the -proposed version of this bug and make sure it's satisfactory for the OEM? Thank you.

Using gnome-control-center 1:3.4.2-0ubuntu0.11 with Precise, I can verify that there is no "Off" option in audio setting window of bluetooth device.

@ James,

Nara help test it. It is good for OEM. Thank you.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package gnome-control-center - 1:3.4.2-0ubuntu0.11

---------------
gnome-control-center (1:3.4.2-0ubuntu0.11) precise; urgency=low

  * Added debian/patches/remove-manual-proxy-in-auto.patch to also remove
    the manual proxy setting when in AUTO mode. (LP: #1100587)

  [ David Henningsson ]
  * debian/patches/96_sound_nua_panel.patch:
    - don't allow to turn bluetooth devices off, or they are dropped from
      the devices list with is no way to turn them back on (lp: #1071561)
 -- Margarita Manterola <email address hidden> Tue, 05 Feb 2013 11:55:06 +0100