Bug 1045234

Summary:	Upstream: bluez5 branch of bluedevil is NOT ready for consumption
Product:	[Fedora] Fedora	Reporter:	Mace Moneta <moneta.mace>
Component:	bluedevil	Assignee:	Jaroslav Reznik <jreznik>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	20	CC:	jgrulich, jreznik, kevin, ltinkl, rdieter, than
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-20 15:54:22 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:

Description Mace Moneta 2013-12-19 23:28:20 UTC

Description of problem:

Connecting or disconnecting bluetooth headphones in KDE causes a segfault.  Upstream indicates that bluez5 bluedevil is a broken branch and should not be used.

https://bugs.kde.org/show_bug.cgi?id=325364

Perhaps this version should be backed out until upstream indicates that the product is ready for inclusion in distributions.

Version-Release number of selected component (if applicable):
bluedevil-2.0.0-0.4.20131015git.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Disconnect/connect bluetooth headphones
2.Segfault
3.Upstream says don't use the bluez5 branch of bluedevil

Actual results:
Segfault

Expected results:
Proper operation; headphones connect and disconnect properly.

Additional info:
Can be worked around by using the command-line bluetoothctl command

Comment 1 Kevin Kofler 2013-12-19 23:41:40 UTC

Backing this out now is impossible.

When our Bluetooth maintainers asked upstream about BlueZ 5 support, he claimed that it'd be ready by the time Fedora 20 releases. Now, Fedora 20 has actually slipped by a few days, so it's even later than when we originally planned to release. Now that Fedora 20 has been released, it is way too late to downgrade the whole BlueZ stack (which affects all desktops, not just KDE). Such decisions have to be made well in advance of the release, and the story upstream told us back then was very different from what he's saying now.

Comment 2 Rex Dieter 2013-12-20 15:54:22 UTC

Indeed, we're collaborating with upstream to resolve issues as soon as possible.

In the meantime, I'd encourage you to try some newer builds:

https://admin.fedoraproject.org/updates/bluedevil