Bug 75489 - explicit swcursor needed during and after install
Summary: explicit swcursor needed during and after install
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-09 00:44 UTC by John Berninger
Modified: 2007-04-18 16:47 UTC (History)
0 users

Fixed In Version: Fedora Core 1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-01-29 08:31:38 UTC
Embargoed:


Attachments (Terms of Use)
output of lspci -vv on system in question (6.81 KB, text/plain)
2002-10-09 00:45 UTC, John Berninger
no flags Details

Description John Berninger 2002-10-09 00:44:36 UTC
Description of Problem:
mouse cursor not recognized properly during or after install


Version-Release number of selected component (if applicable):
Red Hat Linux 8.0

How Reproducible:
always

Steps to Reproduce:
1. install RHL - mouse cursor is a solid white block
2. 
3. 

Actual Results:


Expected Results:
normal mouse cursor

Additional Information:
this happened in 7.1 and 7.2 as well - the installer had a normal cursor, after
install, I had to specify ``Option "SWcursor"'' in the XF86Config file in order
to make the mouse cursor show up normally.  hardware cursors do not work
properly with this hardware.

Comment 1 John Berninger 2002-10-09 00:45:11 UTC
Created attachment 79545 [details]
output of lspci -vv on system in question

Comment 2 Bill Nottingham 2004-01-29 06:06:55 UTC
Does this persist with Fedora Core 1?

Comment 3 Mike A. Harris 2004-01-29 08:31:38 UTC
Problem should be fixed in RHL 9 and later if I recall correctly,
just forgot to close the bug.

Closing as CURRENTRELEASE, however if the problem does persist
in Fedora Core 1, please reopen the bug report, and include
file attachment of X config file, log file individually as
bugzilla file attachments.

Thanks.


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