Bug 1711594

Summary: bluetooth non-functional after F30 upgrade due to incompatibility with dbus-broker (solution identified)
Product: [Fedora] Fedora Reporter: Kevin R. Page <redhat-bugzilla>
Component: bluezAssignee: Don Zickus <dzickus>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: bnocera, dwmw2, dzickus, pasik, spacewar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bluez-5.50-8.fc30 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-18 18:13:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kevin R. Page 2019-05-18 21:12:02 UTC 
Workstation with multiple user accounts and working bluetooth, through Gnome, in Fedora 29.

After upgrade to Fedora 30 bluetooth doesn't work for all-but-one users on console.

The functioning user has the lowest UID, I haven't confirmed this is the reason it works.

For all other users bluetooth is show in Gnome settings as off. The toggle on/off has no effect -- it doesn't stick and the device list doesn't show. In a terminal, hciconfig and lsusb show the bluetooth device, however bluetoothctl times out/cannot access the dongle.

This seems to have been caused by the F30 switch from dbus-daemon to dbus-broker

I've tried two fixes/workaround, both solve the problem:

1) Switch back to dbus-daemon from dbus-broker, i.e.
# systemctl disable dbus-broker.service
# systemctl --global disable dbus-broker.service
# systemctl enable dbus-daemon.service
# systemctl --global enable dbus-daemon.service

After a reboot bluetooth is functional again.

OR

2) Stick with dbus-broker but edit /etc/dbus-1/system.d/bluetooth.conf according to this patch:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=3ef0ce954b66fdf45538a6cdc629f3dac6642832

This also fixes the problem.

bluez git also seems to have switched to this revised configuration upstream, so presumably this will be fixed the next bluez update.

In the meantime could Fedora carry this patch?
Comment 1 Fedora Update System 2019-06-07 08:09:36 UTC 
FEDORA-2019-5101717387 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-5101717387
Comment 2 Fedora Update System 2019-06-08 00:50:57 UTC 
bluez-5.50-8.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-5101717387
Comment 3 Fedora Update System 2019-06-18 18:13:33 UTC 
bluez-5.50-8.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.