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 84367 - Lost keyboard input with AWT_TOOLKIT=MToolkit
Summary: Lost keyboard input with AWT_TOOLKIT=MToolkit
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 5.x
Hardware: All Linux
: P1 blocker (vote)
Assignee: David Simonek
URL:
Keywords: JDK_SPECIFIC
: 83517 89148 138774 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-09-06 20:29 UTC by _ hair
Modified: 2008-12-22 13:56 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ hair 2006-09-06 20:29:29 UTC
Because of the Sun bug
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6429775

I must revert to the old sun.awt.motif.MToolkit renderer.
Since using this sometime after using netbeans, a few minutes, (I suspect it's
related to opening dialogs but have no proof yet) all keyboard input ceases to
be accepted by netbeans. Typing in the editor, typing to navigate in navigation
windows, and shortcut keys.

Xgl is becoming popular amongst linux users and netbeans is getting left behind :'(
Comment 1 _ hair 2006-09-07 10:50:25 UTC
*** Issue 83517 has been marked as a duplicate of this issue. ***
Comment 2 _ hair 2006-09-07 10:54:20 UTC
I suspect this is a duplicate of 
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6465038

but it's crippling NetBeans none the less.

It is indeed related to opening dialogs, and I have a workaround:

One the problem occurs, build the project (ensuring that atleast one class will
not compile) then click in the output window on the linked error message making
sure that class is not the current document in the editor.

When the editor gains focus, switching to the failed class, at the line of the
error, keyboard input is possible again.
Comment 3 Stanislav Aubrecht 2006-09-08 15:29:37 UTC
it's a jdk bug and there's no feasible workaround we could provide in netbeans -
closing
Comment 4 _ hair 2006-09-08 22:14:12 UTC
Fair enough, expected it. Atleast the little workaround there exists for
netbeans is documented somehwere :-)
Comment 5 Marian Mirilovic 2006-11-15 19:26:15 UTC
verified by reporter
Comment 6 Marian Mirilovic 2006-11-15 19:27:21 UTC
*** Issue 89148 has been marked as a duplicate of this issue. ***
Comment 7 David Simonek 2008-07-02 14:52:33 UTC
*** Issue 138774 has been marked as a duplicate of this issue. ***