Bluetooth ON/OFF button switches OFF automatically

Status changed to 'Confirmed' because the bug affects multiple users.

There is a workaround for this:

sudo rfkill unblock bluetooth

I'm seeing this bug on Ubuntu GNOME 13.10

This bug is also present in Ubuntu 14.04 as of 2014-03-27.

Same problem on a Thinkpad X230 running Ubuntu 14.04. This bug was not present on 13.10.

Happens on a Thinkpad T440s running Ubuntu Gnome 14.10.

The issue can also be reproduced on my 14.04, by adding some prints in the source code I found it's cause by a logic trap:

1. we click the switch in the u-c-c bt panel to turn on the bt
2. in the widget's "notify::active" callback it set the BT state to unblocked
3. the BT "state-changed" callback is triggered with {state: unblocked, powered: off}, in this callback it will update the UI
4. in such a case step 2 is triggered again but this time it set the BT state to blocked.

So after a long repetition the final status is BT is turned off again. Actually I'm wondering if it will run into an endless dead loop under special condition.

Anyway in my side I could fix, or maybe only workaround, the issue with the attached patch, it will temporarily block the widget's "notify::active" callback in the bt killswitch callbacks, so we won't run into step 2 after step 3.

forgot to mention the patch is for u-c-c, and I only have it tested on the trusty branch: lp:unity-control-center/14.04

Status changed to 'Confirmed' because the bug affects multiple users.

The attachment "block-power-callback-unless-its-triggered-by-user.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

vivid 15.04 Beta 2 has same bug on lenovo t450s.
The "sudo rfkill unblock bluetooth" workaround seems to work.

Hi guys, I have converted my patch (comment #8) to a merge proposal, could anyone help review it? Thanks in advance.

https://code.launchpad.net/~yuningdodo/unity-control-center/unity-control-center.lp1248720-block-power-callback-unless-its-triggered-by-user/+merge/255041

do you know if that's an issue impacting upstream as well and if it could be sent to GNOME for gnome-control-center?

Let me install a gnome desktop and have a try. Will update later.

I installed gnome desktop on ubuntu trusty, and can also reproduce the issue in gnome-control-center.

The package version is:
gnome-control-center 1:3.6.3-0ubuntu56.1

$ gnome-control-center --version
gnome-control-center 3.6.3

I'll also try with latest upstream version.

The issue is also reproduced in ubuntu gnome daily image [1], the package version is 1:3.14.2-2ubuntu3

[1]: http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/20150407/

Tested with gnome live [1], the issue is not reproduced, the g-c-c version is 3.16.0.

I also checked the source code [2], looks like the issue is already fixed via a redesign [3]. The upstream tracker for the redesign is https://bugzilla.gnome.org/show_bug.cgi?id=719565

[1]: https://download.gnome.org/misc/promo-usb/gnome-3.16.x86_64.iso
[2]: https://git.gnome.org/browse/gnome-control-center/tree/panels/bluetooth/cc-bluetooth-panel.c
[3]: https://git.gnome.org/browse/gnome-control-center/commit/?id=28fecc01c46a7b082f9746744c938e499a522e4f

@Yu, thanks for testing with the newest version, did the redesign address it the same was as you did or differently? In any case should be fine to use your change

@Sebastien, I just made a quick check for the redesigned code, yes, it does similar blocking&unblocking on power_callback(), that is also what my patch does.

This bug was fixed in the package unity-control-center - 15.04.0+15.04.20150410-0ubuntu1

---------------
unity-control-center (15.04.0+15.04.20150410-0ubuntu1) vivid; urgency=medium

  [ Yu Ning ]
  * Block power callback unless it's triggered by the user. (LP:
    #1248720)
 -- CI Train Bot <email address hidden> Fri, 10 Apr 2015 14:09:49 +0000

I could also reproduce this issue on 14.04.2,
unity-control-center version: 14.04.3+14.04.20140922-0ubuntu1

@seb128,

 Could we also put this patch into trusty? Thanks!

@Bin, yes that should be fine, can you update the bug to be SRU compliant (impact/test case/regression potential statements, see https://wiki.ubuntu.com/StableReleaseUpdates) and do a merge proposal against lp:unity-control-center/14.04?
Note that I'm on holidays starting today so you might want to subscribe sponsors or ask on #ubuntu-desktop for sponsoring once it's ready for review

@seb128,

 Sorry for late, I've requested a merge request, thanks for your time!

Hi Bin, we still need the standard info as per comment #25. We can sponsor the update but it will be rejected without the information requested. Let us know once that's done and we will move it forward on our side.

@Will,

 I have updated the description before, but not obviously, I re-updated again, is it ok? :)
 And the source code was already approved now.

 Thanks a lot!

thanks, I've sponsored the SRU, it's waiting for review next

Status changed to 'Confirmed' because the bug affects multiple users.

Hello alkamid, or anyone else affected,

Accepted unity-control-center into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity-control-center/14.04.3+14.04.20150916-0ubuntu1 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!

Tried to reproduce the error on my Dell M15 with Broadcom 4313 wireless card, but I couldn't. It seems the bug only affects Thinkpad notebooks. I tried to force the bug anyway but couldn't find an equivalent of /proc/acpi/ibm/bluetooth for my device. 😞 Hoping somebody'd test and verify the patch soon, so that our friends on Thinkpads can get a better Ubuntu desktop experience.

I've installed the new package from trusty-proposed, the version is 20150916-0ubuntu1.

This bug was fixed in the package unity-control-center - 14.04.3+14.04.20150916-0ubuntu1

---------------
unity-control-center (14.04.3+14.04.20150916-0ubuntu1) trusty; urgency=medium

  [ Ning Yu ]
  * Block power callback unless it's triggered by the user.(LP: #1248720)

  [ CI Train Bot ]
  * No-change rebuild.

 -- Sebastien Bacher <email address hidden> Wed, 16 Sep 2015 09:33:42 +0000

The verification of the Stable Release Update for unity-control-center 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 regressions.

Status changed to 'Confirmed' because the bug affects multiple users.

Ubuntu 14.04 reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm

Further to comment #38, closing Papercuts task