Bug 757963 - blueman no work in F16 KDE spin, dbus error
Summary: blueman no work in F16 KDE spin, dbus error
Keywords:
Status: CLOSED DUPLICATE of bug 757972
Alias: None
Product: Fedora
Classification: Fedora
Component: blueman
Version: 16
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Juan Manuel Rodriguez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-29 04:48 UTC by xset1980
Modified: 2012-04-26 20:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-26 20:58:50 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.