This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 246782

Summary: Loss of reactivity to keystrokes
Product: platform Reporter: Jesse Glick <jglick>
Component: Output WindowAssignee: Jaroslav Havlin <jhavlin>
Status: NEW ---    
Severity: normal CC: JPESKA, mkristofic, mmetelka, sdedic
Priority: P3    
Version: 8.1   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:

Description Jesse Glick 2014-08-29 16:13:52 UTC
Filing in 20140825-9a94e8cb336b but has happened to me from time to time (perhaps once a day) when using dev builds for the past few months. Not sure how to reproduce—what the trigger condition is. Xubuntu 14.04, generally most recent Java 7. Nothing of interest in the log.

After using the IDE for a while, suddenly it stops responding to any keystrokes. Typing letters or arrow keys in the editor, arrow keys in the Projects tab, even Alt-F to post the File menu—nothing happens. (Focus is still displayed, for example as a blinking cursor in the editor.) Keystrokes handled by the window manager (as opposed to the application) still work, as do all mouse events. The only workaround is to restart the IDE.

Today I noticed that in this condition, keystrokes are still processed normally in the Output Window. So for example, after clicking on the OW and getting a blinking caret in it, Page Up/Down scrolls in it. Alt-F even works to post File—but now that the menu is posted, ESC does not work to close it. From the OW, Ctrl-0 opens the editor, but then Ctrl-4 does nothing. Ctrl-TAB switches to the Test Results window, but then you cannot switch back.

(If from the OW I hold press Ctrl-TAB and release TAB while holding down Ctrl to get the window switcher dialog, I can cycle through windows so long as I keep this dialog open, presumably because the OW retains focus. But if I switch to any window other than OW then I cannot reopen it.)

Filing this in the OW component, even though this is a bit backwards: it is the *only* component that is not broken! However given that the OW is a lightweight component, the difference in behavior suggests something wrong in the application rather than at a lower layer (X11, AWT).
Comment 1 Jesse Glick 2014-11-10 17:30:38 UTC
Continues to happen to me in dev builds; happened to me twice in the past couple of hours.
Comment 2 Jaroslav Havlin 2014-11-11 07:00:47 UTC
I haven't experienced this bug, though I work mostly on OS Windows.

CCing Jan Peska (platform/Actions), Milutin Kristofic (editor/Options,Settings), Miloslav Metelka (editor/Actions) and Svata Dedic (editor/Key bindings).