Red Hat Bugzilla – Bug 134033
X server ignores button press events
Last modified: 2007-11-30 17:07:04 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 Description of problem: After running a java-based I/O generator for a while, the system gets into a state where the mouse can be moved and it is possible to type into whichever window currently has the input focus, but no button presses seems to get through. If I rlogin and run xev, I can move the cursor over xev and type. I get event MotionNotify events and KeyPress events, but no ButtonPress events. I can flip to a virtual terminal (and out of the X server) and use the mouse there. I can move it and double-click to select words, for example. I flipped back to the X server and straced it, and it is getting input on the file descriptor associated with the mouse when I press a mouse button, but it looks like it never passes the button press events along. Killing the I/O generator frees things up. Version-Release number of selected component (if applicable): XFree86-4.3.0-35.EL How reproducible: Sometimes Steps to Reproduce: 1.Run a I/O load generator to a half-dozen LUNs. 2.Wait several (maybe 12) hours. 3.Usually, the problem will show up. Additional info:
Is the IO generator available somewhere?
We require additional details and information in able to assess this problem. Without further response, there is nothing we can do to investigate this issue. Please update the bug status. Thanks in advance.
This bug lacks detailed information that is sufficient enough to diagnose the problem, and does not provide enough information to attempt to reproduce the problem or be able to debug the issue. If this is still a problem after applying all of the latest updates for this release of the operating system, contact Red Hat Global Support Services by logging into the Red Hat support website at http://www.redhat.com/support or by contacting support via telephone at 1-888-RED-HAT1 and a support associate will assist you. Thanks in advance. Setting status to "WONTFIX", as there's nothing we can do about this issue as it stands currently.