Bug 12084 - X configuration problems
Summary: X configuration problems
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Brock Organ
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-06-11 14:34 UTC by Brian Ginter
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2000-07-27 18:24:57 UTC

Attachments (Terms of Use)

Description Brian Ginter 2000-06-11 14:34:42 UTC
When setting the resolution during the X confuguration, if you select a 
resolution and then test that setting, occasionally upon return from the 
test, the mouse cursor will get stuck in the upper right corner of the 
screen.  If you continue navigating with the keyboard and test the screen 
resolution again, it will hang in a loop of testing and retesting the 
resolution.  Selecting yes, no or waiting for the 10 second time out all 
produce the same outcome of a retest.

The machine is a PIII-500, Diamond Speedstar A50 using the Mach 64 driver 

Comment 1 Hans de Goede 2000-07-09 21:56:27 UTC
The real problem here is (IMHO) that the installer detected and uses an ps/2
mouse and later on the user selects imps/2 or an other wheelmouse protocol, the
X-test is done with this protocol, and afterwards the mouse is still in this
mode, this confuses X hence the mouse doesn't work anymore.

Comment 2 Glen Foster 2000-07-18 18:27:05 UTC
This defect is considered MUST-FIX for Winston Beta-5

Comment 3 Glen Foster 2000-07-21 18:04:33 UTC
This defect has been re-classified as MUST-FIX for Winston Gold-release

Comment 4 Michael Fulbright 2000-07-27 17:58:56 UTC
Fixed for beta 5 - needs to be tested.

Comment 5 Hans de Goede 2000-07-27 18:05:22 UTC
-did a custom install
-selected imps/2 as mousetype (installer detected 3 button ps2 mouse)
-tested X
-mouse still worked fine after testing

Good job!

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