3.6.4 Vassal - getting java error (out of date - but already have 17 installed and set default..)

Technical Support & Bugs
1

Running vassal.sh after installing and I get the following:

“Error: /usr/bin/java is too old to run this version of Vassal. Please use Java 11 or later.”

I updated Java to 17, set default, and java -version shows 17.

My config:

Linux Mint 19.2 Cinnamon v 4.2.4
Kernel 4.15.0-166-generic
Intel Core i7-7560u- cpu @ 2.4 Ghz x 2
Mem 16GB
Intel gfx

Any ideas?

2

Not really. I have the same Linux distribution and everything works as expected. Did you run the following command (I guess so but better to ask)

#sudo update-alternatives --config java

and select the java version you want?

Maybe you can consider updating the distribution. It shouldn’t be the source of the problem but again, you never know :slight_smile:

3

What is the output of which java?

4

/usr/bin/java I checked /etc/alternatives and it deferences the right Java version

5

Ignore the script. Move into the dir in which vassal is installed and run

java -classpath lib/Vengine.jar VASSAL.launch.ModuleManager

6

Please do not ignore the script. It’s not worth the effort troubleshooting this if we don’t determine what’s wrong and fix it.

Run this from the directory where VASSAL.sh is:

java -classpath lib/Vengine.jar VASSAL.launch.JavaVersionChecker

What output do you get?

7

Sorry, I did not mean to ignore the script permanently. Just to see what happens when starting the program directly. This might be helpful in debugging the script itself, I guess.

8

I ran:

java -classpath lib/Vengine.jar VASSAL.launch.JavaVersionChecker

I got:

Error: Could not find or load main class VASSAL.launch.JavaVersionChecker
Caused by: java.lang.ClassNotFoundException: VASSAL.launch.JavaVersionChecker

9

ran it

Error: Could not find or load main class VASSAL.launch.ModuleManager
Caused by: java.lang.ClassNotFoundException: VASSAL.launch.ModuleManager

10

How did you install VASSAL? It looks to me like you didn’t extract the archive correctly…

11

DL’ed the file, extracted to directory, changed owner and chmod +x …go

I can do it again no problem and see if the replace helps…

12

new download - works perfectly. old DL, fail. Do we need to debug further or chalk it up to missing bits? I guess I can compare dirs to see…

thanks guys - sorry for the ghost

13

i should have done that first – I’ll do so next time :slight_smile:

14

Ok, sounds like you had a bad install.

BTW, there’s nothing in an install that you should need to change ownership of or set the execute bit for. Why are you doing that?

1 Like