Bug 111635 - Mouse pointer not responsive first few seconds
Summary: Mouse pointer not responsive first few seconds
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2003-12-07 06:23 UTC by Clifford Snow
Modified: 2014-03-17 02:40 UTC (History)
2 users (show)

Fixed In Version: FC2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-30 21:09:07 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Clifford Snow 2003-12-07 06:23:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
When booting up with rhgb enabled, the mouse pointer changes from an X
to a pointer.  However, for the first few seconds after the pointer
appears, it does not respond to mouse movement.  

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

How reproducible:

Steps to Reproduce:
1. Boot FC1
2. Wait until mouse pointer changes from an X to a arrow pointer.
3. Attempt to move mouse pointer after pointer appears.

Actual Results:  pointer does not move

Expected Results:  pointer tracks mouse movements.

Additional info:

Comment 1 Warren Togami 2004-03-07 09:51:43 UTC
This is a USB mouse right?  The USB drivers are not loaded
immediately, so I am not sure this can be easily fixed.  Anyhow I
think this is more of an initscript problem and not really rhgb. 

Comment 2 Clifford Snow 2004-03-07 15:01:28 UTC
This is a USB mouse.

Comment 3 Bill Nottingham 2005-09-30 21:09:07 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of

Please try to reproduce this on a current release, such as Fedora Core 4. If the
issue persists, please open a new issue. This should be solved with the 2.6
kernel and the move to the input layer.

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