Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 107230 - Mouse not available during firstboot
Summary: Mouse not available during firstboot
Keywords:
Status: CLOSED DUPLICATE of bug 105627
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-16 00:01 UTC by Marc Deslauriers
Modified: 2007-11-30 22:10 UTC (History)
0 users

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

Attachments (Terms of Use)

Description Marc Deslauriers 2003-10-16 00:01:04 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031013

Description of problem:
During installation on an IBM Thinkpad T30, and selecting a 3-button PS/2 mouse,
the mouse was not available during firstboot. The "X" chaped mouse pointer was
stuck in the middle of the screen and wouldn't move.

As soon as firstboot was finished and gdm came up, the mouse worked.

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

How reproducible:
Always

Steps to Reproduce:
1.Install Fedora Test3 on a T30 thinkpad
2.Select 3 button PS/2 mouse
3.
    

Actual Results:  The mouse doesn't work during firstboot

Expected Results:  A working mouse!

Additional info:

IIRC, this wasn't a problem with test2...
Comment 1 Brent Fox 2003-10-16 00:39:30 UTC 

*** This bug has been marked as a duplicate of 105627 ***
Comment 2 Red Hat Bugzilla 2006-02-21 18:59:11 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.