Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Bluetooth |
Fix Released
|
Medium
|
|||
GNOME Shell |
Fix Released
|
Unknown
|
|||
gnome-bluetooth (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
gnome-shell (Ubuntu) |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) |
Bug Description
See video. I have installed bluetooth, blueman, bluez but it makes no difference to a broken interface to control bluetooth under Gnome 17.10, as shown in the attached video.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: bluetooth 5.46-0ubuntu3
ProcVersionSign
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 17 22:32:30 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-18 (30 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterestingModules: bnep btusb bluetooth
MachineType: LENOVO 20BXCTO1WW
PackageArchitec
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/06/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET54WW (1.19 )
dmi.board.
dmi.board.name: 20BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BXCTO1WW
dmi.product.
dmi.sys.vendor: LENOVO
hciconfig:
summary: |
- bluetooth does not turn on; settings interfaces are nonsensical + Bluetooth icon shows "Off" and the only option given below it is "Turn + Off" |
Changed in bluez (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in gnome-control-center (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in gnome-shell (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in gnome-bluetooth (Ubuntu): | |
status: | New → Confirmed |
Changed in gnome-bluetooth: | |
importance: | Unknown → Low |
status: | Unknown → Confirmed |
Changed in gnome-bluetooth: | |
status: | Confirmed → Invalid |
Changed in gnome-bluetooth: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in gnome-shell: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
tags: | added: bionic |
Changed in gnome-shell: | |
status: | Confirmed → Expired |
tags: |
added: cosmic removed: artful |
tags: | removed: cosmic |
Changed in gnome-bluetooth: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in gnome-shell: | |
importance: | Unknown → Medium |
status: | Unknown → Expired |
Changed in gnome-shell: | |
importance: | Medium → Unknown |
status: | Expired → Unknown |
Changed in gnome-shell (Ubuntu): | |
status: | Confirmed → Fix Committed |
tags: | added: fixed-in-42 fixed-upstream |
Changed in gnome-shell (Ubuntu): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in gnome-shell: | |
status: | Unknown → Fix Released |
Because of the method that the dbus proxies are created there is currently a race condition. When an adapter is added it can have an initial "Powered" state of off which is turned on immediately afterwards. However, the signal connect to get the update only happens later.
This can be easily reproduced on thinkpads by running "rfkill block 0" and "rfkill unblock 0" while looking at the gnome-control- center bluetooth panel.
Attaching a patch that should fix the issue. I hope I didn't totally misunderstand how the whole DBus proxy stuff is supposed to work.