Bug 189596 - Skipping key strokes
Summary: Skipping key strokes
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-21 14:31 UTC by James McManus
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-05-23 13:12:07 UTC


Attachments (Terms of Use)

Description James McManus 2006-04-21 14:31:06 UTC
Description of problem: When type information into an openoffice page, the key
stroke will randomly skip to locations on the page, causing numerous typos and
agrivation.


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

How reproducible:
very

Steps to Reproduce:
1. begin typing
2.
3.
  
Actual results:


Expected results:


Additional info:
This problem also occures with thunderbird and firefox, so I think it is related
to java.

Comment 1 Caolan McNamara 2006-04-21 14:40:48 UTC
Thats sounds really really really unusual, does it happen with any other
applications, e.g. gedit. 

Are you using KDE or GNOME ?

It almost sounds like spurious mouse events being generated from somewhere to
me, maybe even a broken mouse.

Comment 2 Caolan McNamara 2006-04-21 14:41:54 UTC
sorry, you already said it happened with thunderbird/firefox

Comment 3 Caolan McNamara 2006-04-24 09:38:21 UTC
Not OOo specific. Spurious mouse clicks I suspect.

Comment 4 James McManus 2006-04-24 10:57:35 UTC
I am using gnome. I do not been able to reproduce this problem with the gedit.
It seems to only effect OpenOffice, Thunderbird, FireFox, and I also had a
problem with ymessanger. Since it was associated with the first three apps, I
always thought it had something to do with Java, but never determined the actual
problem.

Comment 5 Mike A. Harris 2006-05-23 13:12:07 UTC
Unable to reproduce locally.


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