Bug 62674 - Logitech cordless wheelmouse not recognized
Summary: Logitech cordless wheelmouse not recognized
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mouseconfig
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-04 06:13 UTC by Simon Matter
Modified: 2008-01-17 17:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:48:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Simon Matter 2002-04-04 06:13:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [de] (X11; U; Linux 2.2.19-6.2.16 i686)

Description of problem:
When installing or using mouseconfig, my Logitech cordless wheelmouse is not
recognized as well as other wheel mouses. There is no "generic wheelmouse" in
the menu.

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


How reproducible:
Always

Steps to Reproduce:
1. start mouseconfig
2. try to find the correct mouse type
3. start X and try to use the wheel
	

Actual Results:  Wheel not working.

Expected Results:  Wheel is working.

Additional info:

I was able to select "Micro$oft IntelliMouse (PS/2)" and it worked perfect. But
many mouses don't work with Micro$oft settings. If they all work, it should be
called generic wheel mouse. I don't know how the Mandrake mouse detection works
but it has always worked very well and I whish RedHat includes a similar
mechanism. It's not a big problem for me but for beginners, it can be
frustrating.

Comment 1 Brent Fox 2002-10-10 18:15:00 UTC
I have just completed a text mode interface for redhat-config-mouse, which means
that mouseconfig will be deprecated in the next release of Red Hat Linux.  

Therefore, I will not be putting any development time towards fixing mouseconfig
bugs, so I'm closing this as 'wontfix'.

Comment 2 Red Hat Bugzilla 2006-02-21 18:48:40 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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