Community
Participate
Working Groups
Eclipse does not act upon some keyboard events such as arrow keys, page up / down, home, end when one or more cvs repository locations are defined. I have not enumerated all possible non-working keys, however, alpha numeric keys do work without any exception while the bug affects other keys. Moreover, the mouse cursor that reflects in what client area the mouse cursor is within is not updated in respect to the client window type (e.g. arrow cursor is used in tree views, text cursor is used in text views). Not only does the mouse cursor stay unupdated, but the focus of which client window or component the mouse is interacting with stays unupdated, as well (e.g. an effort to interact with the scrollbar of a source code editor results into painting a text area in the source code editor). This can be temporarily fixed by switching the window with alt+tab and returning to Eclipse using the same key combination (note: only fixes the mouse input problem). Straightforward reproducibility of this bug is hard, since this can occur while leaving Eclipse alone for a moment without interacting with any other applications in the system or the bug can occur while interacting with Eclipse. As soon as all CVS repository locations were removed, the bug was not causing any input problems. Note that restarting Eclipse does not cause the bug to reset. Only restarting the operating system helps. All other applications have not presented any input problems while the bug is active.
May indicate a decorator problem, but I don't think that would explain all symptoms here. Please investigate. Karim, the next time you see this, could you try turning off CVS label decorations and see if that fixes things up? The setting is under Window > Preferences > Workbench > Label Decorations.
The bug was reproducible while all label decorators were disabled. Enabling and disabling the decorator did not cause the bug to go away. However, as soon all projects in the workspace were disconnected from the CVS source control, the bug did not cause any problems, which is in controversy with the original bug report that states that all repository locations have to be removed in order to disable to bug. Note that removing all CVS repository locations was critical the first time.
Moving to Team as the problem occurs independant of the decorators.
See also bug 33931
This problem was NOT caused by any deficiency in Eclipse. After investigating more, a device connected to the computer this problem occured on caused the event handling system of the OS drop to its knees in such way that only Java applications were affected.
