On Thu, Feb 07, 2008 at 04:34:37PM +0100, Александър Л. Димитров wrote: > Hi list, > > let me first say that Sun are incredibly stupid. I mean really. Astoundingly > stupid. Stultifingly stupid. > > This bug > > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6429775 > > has been closed. Which is wrong, this bug should really be open, because it > ain't fixed. I'm using a non-reparenting WM (XMonad) and since they've been so > incredibly unprofessional to hard-code a list of supported WMs into their code > - or something like it - and XMonad is (like any other tiling WM) not part of > that list, it's no good. Anyways, they're relying on all WMs to be reparenting, > which is brain dead. If a WM is not showing up as supported, windows are painted > grey. No widgets, no buttons, no way to interact. > > This has been a known problem for a while. A long while. There exist several > workarounds. One of them is to change the toolkit like this: > > AWT_TOOLKIT=MToolkit java SomeApp.class yeah, its annoying... > > This is wrong, doesn't always work and has bad side effects. It's not working in > my case anyways. > > There was another workaround which I remember having employed several times > successfully already - but I don't remember the details and after a frustrating > Google search it seems the instructions are nowhere to be found. > > It involved sed -i'ing some obscure java-x-lib and removing xinerama extensions > and replacing them with something else, like a dummy parameter. But all this > relys on accurate information about how to do it and I don't know it. Maybe > those are really two unrelated things (one having to do with WM-names, the other > with Xinerama extensions being compiled into X libs..) but I think they were at > least connected. I have xinerama. I need it. > > Does any one of you happen to remember how to resolve this > frustration of mine? I know it's three days later, but you're best bet is to go to #xmonad. A
Attachment:
signature.asc
Description: Digital signature