Bug 757963

Summary:	blueman no work in F16 KDE spin, dbus error
Product:	[Fedora] Fedora	Reporter:	xset1980
Component:	blueman	Assignee:	Juan Manuel Rodriguez <nushio>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	nushio
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:	2012-04-26 20:58:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description xset1980 2011-11-29 04:48:28 UTC

Description of problem:

Blueman cannot init on F16 KDE because of dbus fail



Version-Release number of selected component (if applicable):
blueman-1.21-10.fc16.i686
dbus-1.4.10-3.fc16.i686
dbus-libs-1.4.10-3.fc16.i686
dbus-python-0.83.0-8.fc15.i686
dbusmenu-qt-0.8.2-2.fc16.i686
python-slip-dbus-0.2.17-1.fc16.noarch
dbus-x11-1.4.10-3.fc16.i686
dbus-glib-0.92-2.fc15.i686





How reproducible:
Always

Steps to Reproduce:
1.Kickstart KDE menu
2.Blueman
3.Crash blueman and report in abrt
  
Actual results:

Blueman no work


Expected results:


Additional info:

I tried to use the KDE GUI bluetooth administrator but did not work, no off the device, no on ever, but yes work in terminal using echo '0' > /sys/devices/platform/thinkpad_acpi/bluetooth_enable

Comment 1 xset1980 2011-11-29 04:58:20 UTC

sended information using abrt, bug https://bugzilla.redhat.com/show_bug.cgi?id=757972

Comment 2 Christoph Wickert 2012-04-26 20:58:50 UTC


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