Create account / Log in

Vassal 3.2.17 crash at start

Issues with the Vassal engine.

Moderators: Tim M, uckelman

Vassal 3.2.17 crash at start

Postby yanoo » March 25th, 2020, 10:48 am

Starting by executing `./VASSAL.sh`

Code: Select all
~/VASSAL $ java -version
openjdk version "1.8.0_242"
OpenJDK Runtime Environment (build 1.8.0_242-b08)
OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)


Code: Select all
~/VASSAL $ cat ~/.VASSAL/errorLog
2020-03-25 11:36:32,618 [0-main] INFO  VASSAL.launch.StartUp - Starting
2020-03-25 11:36:32,621 [0-main] INFO  VASSAL.launch.StartUp - OS Linux 5.5.10-200.fc31.x86_64
2020-03-25 11:36:32,621 [0-main] INFO  VASSAL.launch.StartUp - Java version 1.8.0_242
2020-03-25 11:36:32,621 [0-main] INFO  VASSAL.launch.StartUp - VASSAL version 3.2.17
2020-03-25 11:36:32,680 [0-AWT-EventQueue-0] INFO  VASSAL.launch.ModuleManager - Manager
2020-03-25 11:36:32,695 [0-AWT-EventQueue-0] ERROR VASSAL.tools.ErrorDialog -
java.lang.ExceptionInInitializerError: null
   at VASSAL.launch.ModuleManager.launch(ModuleManager.java:455) ~[Vengine.jar:na]
   at VASSAL.launch.ModuleManager$2.run(ModuleManager.java:342) ~[Vengine.jar:na]
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) ~[na:1.8.0_242]
   at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) ~[na:1.8.0_242]
   at java.awt.EventQueue.access$500(EventQueue.java:97) ~[na:1.8.0_242]
   at java.awt.EventQueue$3.run(EventQueue.java:709) ~[na:1.8.0_242]
   at java.awt.EventQueue$3.run(EventQueue.java:703) ~[na:1.8.0_242]
   at java.security.AccessController.doPrivileged(Native Method) ~[na:1.8.0_242]
   at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74) ~[na:1.8.0_242]
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) ~[na:1.8.0_242]
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205) [na:1.8.0_242]
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) [na:1.8.0_242]
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) [na:1.8.0_242]
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) [na:1.8.0_242]
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) [na:1.8.0_242]
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) [na:1.8.0_242]
Caused by: java.awt.HeadlessException: null
   at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:204) ~[na:1.8.0_242]
   at java.awt.Window.<init>(Window.java:536) ~[na:1.8.0_242]
   at java.awt.Frame.<init>(Frame.java:420) ~[na:1.8.0_242]
   at java.awt.Frame.<init>(Frame.java:385) ~[na:1.8.0_242]
   at javax.swing.JFrame.<init>(JFrame.java:189) ~[na:1.8.0_242]
   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


OS: Fedora 31
Processor: Intel® Core™ i7-8550U CPU
Graphics: Intel® UHD Graphics 620
yanoo
 
Posts: 1
Joined: March 25th, 2020, 10:41 am

Re: Vassal 3.2.17 crash at start

Postby uckelman » March 25th, 2020, 10:18 pm

Thus spake yanoo:
> [na:1.8.0_242] Caused by: java.awt.HeadlessException: null at
> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:204)

You're running using a headless Java, i.e., one which doesn't have any
graphics display capabilities.

You said that you're using Fedora 31, so the package you have installed
will be called java-1.8.0-openjdk-headless. The package you need to
install additionally is called java-1.8.0-openjdk.

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8345
Joined: December 10th, 2007, 9:48 am
Location: Durham, England


Return to Technical Support & Bugs

Who is online

Users browsing this forum: No registered users and 2 guests