Bug 333841 - Bluetooth mouse sensitivity not controllable
Summary: Bluetooth mouse sensitivity not controllable
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 8
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-10-16 10:18 UTC by srh
Modified: 2009-01-09 07:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 07:19:18 UTC
Type: ---

Attachments (Terms of Use)

Description srh 2007-10-16 10:18:03 UTC
Description of problem:
I have a standard Dell M1330 laptop, and bought a standard Dell bluetooth mouse
with it. After ressing the blue button on the mouse, running 'hidd --search'
associates the mouse with the laptop and it works fine.

However, the bluetooth mouse is too sensitive in that moving the mouse flicks
the cursor across the screen too fast. Adjusting 'Mouse preferences' in Gnome to
lower acceleration and sensitivity lowers the touchpad speed, but makes no
difference to the bluetooth mouse. Running various settings using xset on the
command line makes no difference to the bluetooth mouse speed either.

As a result, using the bluetooth mouse is not really possible.

Bluetooth mouse info...
'hidd --show'
00:07:61:94:2D:51 Logitech   (3) Button Mouse [046d:b006] connected

I'm unsure which fedora package this bug applies to.

Version-Release number of selected component (if applicable):
This applies to Fedora 8 test 3 and Fedora 7.

How reproducible:
Every time

Steps to Reproduce:
1. Connect up bluetooth mouse.
2. Adjust acceleration and sensitivity in gnome 'Mouse Preferences"
3. No effect on bluetooth mouse (but does affect the touchpad as expected).
Actual results:
No control over bluetooth mouse sensitivity/resolution.

Expected results:
Cursor should go slower or faster as acceleration/sensitivity bar adjusted.

Comment 1 Ondrej Vasik 2007-10-18 15:59:13 UTC
I think correct component is control-center - but it is possible that there will
be necessary some changes in some other packages like bluez or gnome-bluetooth.
Changing component to control-center.

Comment 2 Bastien Nocera 2007-10-18 16:26:29 UTC
If xset doesn't work, then it's an X bug. The control-center should get support
for doing this sort of thing (handling different sensitivities, etc.) on
different devices once input device hotplugging support is in X.

Comment 3 Bug Zapper 2008-11-26 07:59:24 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 4 Bug Zapper 2009-01-09 07:19:18 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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