Vassal 3.2.9 crashes on Ubuntu 12.04 when starting

When I try to start Vassal 3.2.9 (i just downloaded and unpacked it) it crashes (Unexpected Exception)

Model: Lenovo Thinkpad Edge E335
OS: Ubuntu 12.04 (64-bit)
CPU: AMD E2-1800 APU with Radeon™ HD Graphics × 2
Memory: 3GB
Video: VESA: HONDO (I think i only have a onboard grafik card.!?)
VASSAL: 3.2.9
Java: OpenJDK 7
Module: none

The log from the crash

2014-01-08 16:47:50,802 [0-main] INFO VASSAL.launch.StartUp - Starting 2014-01-08 16:47:50,816 [0-main] INFO VASSAL.launch.StartUp - OS Linux 3.2.0-58-generic 2014-01-08 16:47:50,816 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_25 2014-01-08 16:47:50,817 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.9 2014-01-08 16:47:51,814 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager 2014-01-08 16:47:52,499 [0-AWT-EventQueue-0] ERROR VASSAL.tools.ErrorDialog - java.lang.ExceptionInInitializerError: null at VASSAL.tools.image.ImageUtils.<clinit>(ImageUtils.java:246) ~[Vengine.jar:na] at VASSAL.tools.ApplicationIcons.<clinit>(ApplicationIcons.java:105) ~[Vengine.jar:na] at VASSAL.launch.ModuleManagerWindow.<init>(ModuleManagerWindow.java:184) ~[Vengine.jar:na] at VASSAL.launch.ModuleManagerWindow.<clinit>(ModuleManagerWindow.java:178) ~[Vengine.jar:na] at VASSAL.launch.ModuleManager.launch(ModuleManager.java:500) ~[Vengine.jar:na] at VASSAL.launch.ModuleManager$2.run(ModuleManager.java:347) ~[Vengine.jar:na] at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) ~[na:1.7.0_25] at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733) ~[na:1.7.0_25] at java.awt.EventQueue.access$200(EventQueue.java:103) ~[na:1.7.0_25] at java.awt.EventQueue$3.run(EventQueue.java:694) ~[na:1.7.0_25] at java.awt.EventQueue$3.run(EventQueue.java:692) ~[na:1.7.0_25] at java.security.AccessController.doPrivileged(Native Method) ~[na:1.7.0_25] at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) ~[na:1.7.0_25] at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) ~[na:1.7.0_25] at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) ~[na:1.7.0_25] at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) ~[na:1.7.0_25] at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) ~[na:1.7.0_25] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) ~[na:1.7.0_25] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) ~[na:1.7.0_25] at java.awt.EventDispatchThread.run(EventDispatchThread.java:91) ~[na:1.7.0_25] Caused by: java.lang.IllegalStateException: null at VASSAL.tools.image.ImageIOImageLoader.<clinit>(ImageIOImageLoader.java:117) ~[Vengine.jar:na] ... 20 common frames omitted

Thanks in advance for helping

Thus spake MetaSystem:

When I try to start Vassal 3.2.9 (i just downloaded and unpacked it) it
crashes (Unexpected Exception)

Model: Lenovo Thinkpad Edge E335 OS: Ubuntu 12.04 (64-bit) CPU: AMD
E2-1800 APU with Radeon™ HD Graphics Memory: 3GB Video: VESA: HONDO
(I think i only have a onboard grafik card.!?) VASSAL: 3.2.9 Java:
OpenJDK 7 Module: none

We’re aware of the problem:

vassalengine.org/tracker/sho … i?id=10723

It’s a collision between our workaround for a bug in some versions of
Java and some other versions of Java being broken in a way we didn’t
expect. This will be fixed in 3.2.10.


J.

Ahh, big thanks for the fast response!
Is there - in the mean time - a way to downgrade java (or vassal) so that it works?
Or will 3.2.10 soon be published?

Thus spake MetaSystem:

Ahh, big thanks for the fast response!
Is there - in the mean time - a way to downgrade java (or vassal) so
that it works?

The only versions of Java for which we’ve seen this bug are Java 7 Update
21 and Java 7 Update 25. I don’t have the problem myself with Java 7
Update 45. So if you can use a newer version of Java, you’ll likely be
able to avoid the bugs entirely (both the bug in our workaround and the
bug in Java).

Alternatively, you could use the current development build,
3.2.10-svn8974:

vassalengine.sourceforge.net/builds/

It has a workaround workaround which at least lets you run VASSAL—
though you might find that a few rare JPEGs are very oddly colored.

I do not recommend going back to 3.2.8, as it has some serious bugs
which are fixed in 3.2.9.

Or will 3.2.10 soon be published?

I figure we will release 3.2.10 once we’ve fixed this bug and wrapped
up some ongoing work with the Mac bundle, so it shouldn’t be very long.


J.