Bug 86461 - Mouse stops functioning after selecting a model during setup
Summary: Mouse stops functioning after selecting a model during setup
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 8.0
Hardware: i586
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2003-03-22 22:30 UTC by Mike
Modified: 2007-04-18 16:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-10-05 03:07:54 UTC

Attachments (Terms of Use)

Description Mike 2003-03-22 22:30:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 

Description of problem:
Serial mouse was working fine during setup, but at the Mouse Configuration 
screen it stopped working after I selected the "Microsoft Rev 2.1A or higher 
(serial)" driver.

Had a similar problem when configuring the mouse model in GNOME on another 
machine.  Mouse stopped working until machine was rebooted.

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

How reproducible:

Steps to Reproduce:
1.  Connect a serial mouse, Rev 2.1A or higher.
2.  At Mouse Configuration screen, change the default serial mouse to this 
3.  Click Next and mouse stops working.

Actual Results:  Mouse stops working, have to reboot to get functionality back.

Expected Results:  Mouse continues to work.

Additional info:

Comment 1 Michael Fulbright 2003-03-24 17:54:10 UTC
Is this the Mouse Configuration screen in the installation program, or one you
run after installation and reboot?

Comment 2 Mike 2003-03-25 02:30:11 UTC
It's the Mouse Configuration screen in the installation program.

Comment 3 Michael Fulbright 2003-04-02 20:22:17 UTC
Matt is this the issue you fixed for Red Hat Linux 9?

Comment 4 Matt Wilson 2003-04-02 20:35:24 UTC
usually this is because the mouse gets set in "generic 3 button mouse" or
"Intellimouse" protocol, when the machine is expecting the opposite.  This
should be better in Red Hat Linux 9, but I do not know if it will fix this exact
problem or not.

Comment 5 Jeremy Katz 2004-10-05 03:07:54 UTC
With the completely different input subsystem in the 2.6 kernel, this
shouldn't be an issue any longer.

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