mad@unserver.de writes:

Hi,

Am Tue, 17 Mar 2009 13:22:30 -0700 schrieb Kendall Shaw :

...

I have to use some applications that use swing, e.g. intellij IDEA. Sometimes the keyboard stops working for them.

I have both AMT_TOOLKIT=MToolkit environment variable and I have setWMName "LG3D" in Hooks/EwmhDesktops.hs, but I still have the keyboard problem.

Are there any other work arounds?

After the comment on issue 177 earlier today, I tried the patch, too, and it seems to work for me (xmonad-darcs, jdk 1.6.0_11). Maybe you'll have luck with it, too: it's the "failed fix attempt" at comment #2 http://code.google.com/p/xmonad/issues/detail?id=177

I just had the keyboard stop working again. So, that patch doesn't fix the non-working keyboard problem. Kendall

Kendall, AWT_TOOLKIT=MToolkit does not work well and introduce many problems to java apps, to solve the gray window problem use just the setWMName workaround. There's another known problem with java issue 177http://code.google.com/p/xmonad/issues/detail?id=177, java apps appear to receive focus but keyboard doesn't work until user clicks on the window. Have not applied the patch yet, but it seems to solve this. Henrique G. Abreu On Wed, Apr 1, 2009 at 14:46, Kendall Shaw https://mail.google.com/mail?view=cm&tf=0&to=kshaw@kendallshaw.com

wrote:

I think the problem I experienced is a result of setting AWT_TOOLKIT=MToolkit. I noticed that I get the same non-working keyboard in whatever KDE's window manager is. Unsetting that environment variable, I have not had the non-working keyboard in xmonad so far.

So, I first set AWT_TOOLKIT which fixed the grey window problem. Then I tried setting setWMName to LG3D in EwmhDesktops.hs, but left AWT_TOOLKIT set, which seems to cause the non-working keyboard problem.

Kendall _______________________________________________ xmonad mailing list xmonad@haskell.orghttps://mail.google.com/mail?view=cm&tf=0&to=xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

Santanu Chatterjee writes:

On Wed, Mar 18, 2009 at 1:52 AM, Kendall Shaw wrote:

...

I have both AMT_TOOLKIT=MToolkit environment variable and I have ^^^^^^^^ Shouldn't this be AWT_TOOLKIT ?

Yes, I made the typo in the email. AWT_TOOLKIT for AWT is what I have set. Kendall