Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 452924 - bluetooth-properties crashes when adding bluetooth mouse as input device, leaving device inoperable in X
Summary: bluetooth-properties crashes when adding bluetooth mouse as input device, lea...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-25 22:07 UTC by Adrian Worthington
Modified: 2008-07-08 20:42 UTC (History)
1 user (show)

Fixed In Version: 2.6.25.9-76.fc9.x86_64
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-08 20:38:19 UTC


Attachments (Terms of Use)
gdb backtrace from adding input device using bluetooth-properties applet (deleted)
2008-06-25 22:10 UTC, Adrian Worthington
no flags Details

Description Adrian Worthington 2008-06-25 22:07:49 UTC
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 22:10:59 UTC
Created attachment 310302 [details]
gdb backtrace from adding input device using bluetooth-properties applet

Comment 2 Adrian Worthington 2008-06-25 22:12:31 UTC
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 20:42:06 UTC
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.