Bug 119707 – wireless mouse tracks too fast

Bug 119707 - wireless mouse tracks too fast

Summary:	wireless mouse tracks too fast

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	control-center (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	i386 Linux

Priority	low Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Ray Strode [halfline]
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-04-01 12:43 EST by Maxwell Bottiger
Modified:	2007-11-30 17:10 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-05-13 13:23:05 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Maxwell Bottiger 2004-04-01 12:43:00 EST

Description of problem:
I'm using a wireless logitech wheel mouse and it's tracking speed is
way too high.  I'd like to know if it's possible to give a greater
range to the adjustment in mouse acceleration menu in GNOME's prefs.

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


How reproducible:
Always there

Steps to Reproduce:
1.control-center-2.5.2-3
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ray Strode [halfline] 2005-05-12 11:53:06 EDT

Hi,
I'm going through bugs assigned to me and attempting to clean some of the older,
fixed ones up.

This bug hasn't changed in over a year old now.  Are you still seeing the problem? 

(This a batch message is being sent to all my bugs that haven't changed in a year)

Comment 2 Maxwell Bottiger 2005-05-13 12:40:55 EDT

If I remember right, this problem was fixed with the next update of fedora core.
 I don't know if anyone addressed it directly or it just was fixed
coincidentally, but it works ok now.  You should probably just close this bug out.

Comment 3 Ray Strode [halfline] 2005-05-13 13:23:05 EDT

Thanks.

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