I used to be able to run VASSAL on my CentOS 6.5 Linux machine with no problems. I then replaced my OS with Fedora 21 but kept my home directories (including the VASSAL installation) unmodified. Now when I try to launch VASSAL.sh it just hangs.
I confirmed that my default java is up to date:
[dleclair@dleclair-lptp VASSAL-3.2.11]$ java -version
openjdk version "1.8.0_25"
OpenJDK Runtime Environment (build 1.8.0_25-b18)
OpenJDK 64-Bit Server VM (build 25.25-b02, mixed mode)
[dleclair@dleclair-lptp VASSAL-3.2.11]$
When I check the VASSAL error log, I see the following exception being thrown:
[dleclair@dleclair-lptp VASSAL-3.2.11]$ cat ~/.VASSAL/errorLog
2014-12-28 08:18:17,020 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-12-28 08:18:17,022 [0-main] INFO VASSAL.launch.StartUp - OS Linux 3.17.7-300.fc21.x86_64
2014-12-28 08:18:17,022 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_25
2014-12-28 08:18:17,022 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.11
2014-12-28 08:18:17,082 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2014-12-28 08:18:17,104 [0-AWT-EventQueue-0] ERROR VASSAL.tools.ErrorDialog -
java.lang.ExceptionInInitializerError: null
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:311) ~[na:1.8.0_25]
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:744) ~[na:1.8.0_25]
at java.awt.EventQueue.access$400(EventQueue.java:97) ~[na:1.8.0_25]
at java.awt.EventQueue$3.run(EventQueue.java:697) ~[na:1.8.0_25]
at java.awt.EventQueue$3.run(EventQueue.java:691) ~[na:1.8.0_25]
at java.security.AccessController.doPrivileged(Native Method) ~[na:1.8.0_25]
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75) ~[na:1.8.0_25]
at java.awt.EventQueue.dispatchEvent(EventQueue.java:714) ~[na:1.8.0_25]
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) [na:1.8.0_25]
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) [na:1.8.0_25]
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) [na:1.8.0_25]
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) [na:1.8.0_25]
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) [na:1.8.0_25]
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) [na:1.8.0_25]
Caused by: java.awt.HeadlessException: null
at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:207) ~[na:1.8.0_25]
at java.awt.Window.<init>(Window.java:536) ~[na:1.8.0_25]
at java.awt.Frame.<init>(Frame.java:420) ~[na:1.8.0_25]
at java.awt.Frame.<init>(Frame.java:385) ~[na:1.8.0_25]
at javax.swing.JFrame.<init>(JFrame.java:181) ~[na:1.8.0_25]
at VASSAL.launch.ModuleManagerWindow.<init>(ModuleManagerWindow.java:180) ~[Vengine.jar:na]
at VASSAL.launch.ModuleManagerWindow.<clinit>(ModuleManagerWindow.java:178) ~[Vengine.jar:na]
... 16 common frames omitted
[dleclair@dleclair-lptp VASSAL-3.2.11]$
I’m wondering if it’s somehow not happy with the VASSAL modules that get loaded by default. Is there a way that I can launch VASSAL such that it forgets the modules that I had there before?