Thus spake Joel Uckelman: > > (I've already sent a version of this to Todd; here's an update for those > playing along at home.) > > Short version: > > This problem has nothing to do with the Tunisia module, memory settings, > or VASSAL. It's a problem with Java, and it only affects Linux users > running particular window managers. > > Long version: > > If you're using a non-reparenting window manager on Linux---Beryl, Compiz, > and Compiz Fusion are all examples of these---then you might find that some > windows in VASSAL either lack some of the widgets (buttons, scroll bars, > etc.), are unable to display images, or both. > > This is due to some bad code in the JVM, as discussed here: > > http://bugs.sun.com/view_bug.do?bug_id=6509038 > > There's nothing we can do about this on the VASSAL end of things---we're > stuck waiting for Sun (or, now people contributing code to the open-source > Java 7) to fix this. > > This probably doesn't affect all that many people---Linux users who > are using compositing window managers, mainly---but if you're one of > them, now you know why it's happening. Ultimately, the fix will involve > upgrading to some version of Java 7. For reference, it's not fixed in > 1.7.0.0-0.19.b21, which is what I'm using on my Fedora 8 system. >
More follow-up: It's possible to run VASSAL within Xnest or Xephyr if you're using a non-reparenting window manager. -- J.
