Bug 1348669

Summary:	blueman-applet unable to enable bluetooth
Product:	[Fedora] Fedora	Reporter:	Stuart D Gathman <stuart>
Component:	bluez	Assignee:	Don Zickus <dzickus>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	dwmw2, dzickus, fedora, jan.kratochvil, marcel, projects.rg
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-29 23:36:08 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 Stuart D Gathman 2016-06-21 17:31:36 UTC

Description of problem:
Clicking on "Enable bluetooth" does nothing.  After issuing "power on" in bluetoothctl, blueman will make connections - but it still thinks bluetooth is turned off!  (Even though the icon now shows it is active.)

Version-Release number of selected component (if applicable):
blueman-2.0.4-2.fc24.x86_64
cinnamon-3.0.5-2.fc24.x86_64

How reproducible:
always

Steps to Reproduce:
1. Boot laptop or insert USB bluetooth dongle
2. Attempt to enable bluetooth from applet in cinnamon
3. 

Actual results:
Enable bluetooth does nothing

Expected results:
Bluetooth powered on and enabled

Additional info:
Issuing "power on" from bluetoothctl enables bluetooth, and blueman-applet will then perform its other functions - but still says bluetooth is disabled!

Will test from MATE DE at some point.

Comment 1 leigh scott 2016-06-21 17:56:40 UTC

Blueman isn't my problem any more as I have orphaned it because the current state of bluez5 is shit, no even beta quality IMO

There is a udev fix here
 
https://bugzilla.redhat.com/show_bug.cgi?id=1348346#c10

Comment 2 Stuart D Gathman 2016-06-21 18:03:47 UTC

I actually don't want bluetooth powered on at boot (I'm a power miser).  Having it powered on manually is what you want for mobile devices.  I just want the button in blueman-applet to work, so as not to have to open a terminal and run bluetoothctl.  Yeah, I could supply a clickable launcher to run bluetoothctl, but it seems pretty clear that there is some kind of simple bug with blueman-applet.

Maybe I'm mistaken, but if bluetoothctl works, doesn't that mean that bluez is working, and gui problems are in the gui?  Doesn't the gui essentially do the same things as bluetoothctl - but with buttons instead of commands?

Comment 3 Stuart D Gathman 2016-08-29 23:36:08 UTC

Apparently, bluez and blueman now expect udev to power on bluetooth adapters.  But no udev rules are supplied by default.

*** This bug has been marked as a duplicate of bug 1348346 ***