Bluetooth cannot be turned on once turned off

Bug #1857787 reported by Orestis Gorgas on 2019-12-29
40
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Undecided
Unassigned
gnome-control-center (Ubuntu)
Low
Unassigned

Bug Description

Given that Bluetooth is disabled,
And I want to enable the bluetooth,
When I open the Bluetooth tab in Settings
And I press the button,
Then the button background turns green but the handle does not move (State 1- Bug 1)

Being at State 1,
When I move to another tab,
And I come back to the "Bluetooth" tab
Then the Bluetooth is enabled and I can choose a bluetooth device. (State 2)

Being at State 2,
When I disable the Bluetooth
And I start the process from the beginning
Then I cannot re-enable the Bluetooth

Ubuntu version: Ubuntu 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-bluetooth 3.34.0-1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 29 01:12:53 2019
InstallationDate: Installed on 2019-06-22 (189 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-bluetooth
UpgradeStatus: Upgraded to eoan on 2019-11-01 (57 days ago)

Orestis Gorgas (orestis-gorgas) wrote :
Daniel van Vugt (vanvugt) wrote :

Please use the command 'rfkill' to find the ID of your Bluetooth device, then try:

  rfkill block ID
  rfkill unblock ID

to turn it off/on manually. Does that work?

Changed in gnome-bluetooth (Ubuntu):
status: New → Incomplete
Orestis Gorgas (orestis-gorgas) wrote :

yes

Daniel van Vugt (vanvugt) wrote :

OK thanks. Then this sounds like a GUI-only problem.

Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → New
affects: gnome-shell (Ubuntu) → gnome-control-center (Ubuntu)
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Can you include a screenshot showing the wrong status and a 'journalctl -b 0' log after getting the problem?

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
Changed in gnome-control-center (Ubuntu):
status: Incomplete → Confirmed
tags: added: focal
removed: eoan
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers