Blutooth on/off does not work properly from gnome-control-center

Bug #1933221 reported by Andy Chi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OEM Priority Project
New
Critical
Andy Chi
bluez (Ubuntu)
Fix Released
High
Daniel van Vugt
Focal
Fix Released
High
Andy Chi
Hirsute
Fix Released
High
Andy Chi
Impish
Fix Released
High
Daniel van Vugt

Bug Description

[Impact]

On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore.

[Test Plan]

1. Open gnome-control-center and select Bluetooth
2. Turn off Bluetooth via UI
3. Turn on Bluetooth via UI

Expect: Device list appears, so Bluetooth really is on.

[Where problems could occur]

Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting.

[Other info]

Upstream bug in gnome-bluetooth:
https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

Discussion in linux-bluetooth:
https://marc.info/?t=162004758900003&r=1&w=2

Revision history for this message
Andy Chi (andch) wrote :
tags: added: oem-priority originate-from-1931048 somerville
Changed in oem-priority:
assignee: nobody → Andy Chi (andch)
importance: Undecided → Critical
Revision history for this message
Andy Chi (andch) wrote :

update debdiff of groovy.

Revision history for this message
Andy Chi (andch) wrote :

upload debdiff of hirsute

Changed in bluez (Ubuntu):
status: New → Fix Committed
importance: Undecided → High
Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you need 20.10? I don't think we have kernels that trigger the issue on that serie and I don't think it's worth the effort since it's non-LTS and not-current-stable?

Upload to hirsute and focal now with the bug reference added to the changelog as required by the SRU process

We will handle impish as we update bluez to the current upstream version

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the fix, but please be more careful to check for existing bugs (bug 1926062) in future rather than opening new ones.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Since the fix isn't in impish yet and that has to come first, we have time to clean up the duplicate bugs. Please use bug 1926062 instead.

Revision history for this message
Andy Chi (andch) wrote :

Hi @Daniel,
Sorry for that, I tried to search for existing bug, I guess I'm not using the right words to search. Will be careful next time or ask in mattermost channel first. Thanks.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

In a case like this it might have been easier to find just by searching for bluez bugs and ordering them newest-to-oldest. When you do that, bug 1926062 is near the top.

Revision history for this message
Andy Chi (andch) wrote :

Got it, thanks for sharing.

Revision history for this message
Sebastien Bacher (seb128) wrote :

@Daniel, I'm undupping, the bug is referenced in the SRUes uploaded and I don't intend to a reject/rebuild/fix the vcs etc dance only to change the reference

Revision history for this message
Robie Basak (racb) wrote :

See bug 1926062 for previous SRU review.

Revision history for this message
Robie Basak (racb) wrote : Please test proposed package

Hello Andy, or anyone else affected,

Accepted bluez into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.56-0ubuntu4.2 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 on 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, what testing has been performed on the package and change the tag from verification-needed-hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in bluez (Ubuntu Hirsute):
status: New → Fix Committed
tags: added: verification-needed verification-needed-hirsute
Changed in bluez (Ubuntu Focal):
status: New → Fix Committed
tags: added: verification-needed-focal
Revision history for this message
Robie Basak (racb) wrote :

Hello Andy, or anyone else affected,

Accepted bluez into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.3 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 on 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Andy Chi (andch) wrote :

[OS version]
Focal

[kernel version]
5.13-oem

[Step]
1. open gnome-settings
2. turn off Bluetooth by toggle
3. turn on Bluetooth by toggle

It works fine.

tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
Andy Chi (andch) wrote :

[OS version]
Hirsute

[kernel version]
5.11.0-16-generic

[Step]
1. open gnome-settings
2. turn off Bluetooth by toggle
3. turn on Bluetooth by toggle

It works fine.

tags: added: verification-done verification-done-hirsute
removed: verification-needed verification-needed-hirsute
Changed in bluez (Ubuntu):
status: Fix Committed → Fix Released
Changed in bluez (Ubuntu Focal):
assignee: nobody → Anch (anch)
Changed in bluez (Ubuntu Hirsute):
assignee: nobody → Andy Chi (andch)
Changed in bluez (Ubuntu Impish):
assignee: nobody → Daniel van Vugt (vanvugt)
Changed in bluez (Ubuntu Focal):
assignee: Anch (anch) → Andy Chi (andch)
description: updated
Changed in bluez (Ubuntu Focal):
importance: Undecided → High
Changed in bluez (Ubuntu Hirsute):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluez - 5.56-0ubuntu4.2

---------------
bluez (5.56-0ubuntu4.2) hirsute; urgency=medium

  * debian/patches/0001-fix-reading-from-rfkill-socket.patch:
    - fix reading from rfkill socket (lp: #1933221)

 -- Andy Chi <email address hidden> Tue, 22 Jun 2021 08:07:12 +0000

Changed in bluez (Ubuntu Hirsute):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for bluez has completed successfully and the package is now being 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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluez - 5.53-0ubuntu3.3

---------------
bluez (5.53-0ubuntu3.3) focal; urgency=medium

  * debian/patches/0001-fix-reading-from-rfkill-socket.patch:
    - fix reading from rfkill socket (lp: #1933221)

 -- Andy Chi <email address hidden> Tue, 22 Jun 2021 14:27:12 +0800

Changed in bluez (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Mic159 (mic159) wrote :

This has caused bluetooth to become completely unavailable on my Dell XPS 13 9300.
gnome-control-center says "No Bluetooth Found", "Plug in a gongle to use Bluetooth."

Downgrading the package back to 5.56-0ubuntu4.1 resolves the issue.

I am using ubuntu 21.04.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for letting us know. Please open a new bug about that by running:

  ubuntu-bug bluez

Revision history for this message
Andy Chi (andch) wrote (last edit ):

Hi @mic159,
Can you also help to append sos report, BIOS version, `rfkill list` and `lspci -nnvv` in the new bug?
Thanks.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Now is a good time to mark this as a duplicate of bug 1926062 since they're the same bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.