Bug 111635

Summary: Mouse pointer not responsive first few seconds
Product: [Fedora] Fedora Reporter: Clifford Snow <glass-art>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED CURRENTRELEASE QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: rvokal, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: FC2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-30 21:09:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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)
Gecko/20031114

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):
rhgb-0.11.2-1

How reproducible:
Always

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. 
Reassigning.


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
response.

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.