Bug 452924 - bluetooth-properties crashes when adding bluetooth mouse as input device, leaving device inoperable in X
bluetooth-properties crashes when adding bluetooth mouse as input device, lea...
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
9
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-25 18:07 EDT by Adrian Worthington
Modified: 2008-07-08 16:42 EDT (History)
1 user (show)

See Also:
Fixed In Version: 2.6.25.9-76.fc9.x86_64
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-08 16:38:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
gdb backtrace from adding input device using bluetooth-properties applet (8.19 KB, application/octet-stream)
2008-06-25 18:10 EDT, Adrian Worthington
no flags Details

  None (edit)
Description Adrian Worthington 2008-06-25 18:07:49 EDT
Description of problem:

The gnome bluetooth-properties panel crashes when trying to add an input device
(a bluetooth mouse), although this could be a problem with a lower level of the
stack.

When trying to add the device which is in the Bonded Devices window. Go to
Services->Input->Add select the mouse device and click connect. After a period
of time has passed the properties panel crashes, and the following messages are
in the syslog

Jun 25 22:44:02 localhost hcid[7118]: GetRemoteServiceHandles:
org.freedesktop.DBus.Error.NoReply(Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.)
Jun 25 22:44:17 localhost hcid[7118]: connect(): Connection timed out (110)
Jun 25 22:48:51 localhost hcid[7118]: GetRemoteServiceHandles:
org.freedesktop.DBus.Error.NoReply(Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.)
Jun 25 22:49:06 localhost hcid[7118]: connect(): Connection timed out (110)

The backtrace log is attached to the bug report.


Version-Release number of selected component (if applicable):

current patched fedora 9

$ rpm -q bluez-gnome
bluez-gnome-0.26-1.fc9.x86_64

$ rpm -q bluez-libs
bluez-libs-3.32-1.fc9.x86_64

How reproducible:


Steps to Reproduce:
1. Start bluetooth-properties
2. Add Input Device from Services->Input Service->Add-Connect

  
Actual results:

Crash

Expected results:

Mouse is added as a HID device and useable in X.

Additional info:
Comment 1 Adrian Worthington 2008-06-25 18:10:59 EDT
Created attachment 310302 [details]
gdb backtrace from adding input device using bluetooth-properties applet
Comment 2 Adrian Worthington 2008-06-25 18:12:31 EDT
It is worth noting that this bug seems very similar to #447299 although I get
very different messages in my syslog.
Comment 3 Adrian Worthington 2008-07-08 16:42:06 EDT
Updating to the latest kernel 2.6.25.9-76.fc9 fixed the problem and the
bluetooth mouse works successfully with this release.

Note You need to log in before you can comment on or make changes to this bug.