3.2.13 will not launch under Ubuntu 14.04

Whenever I click on the VASSAL.sh file, it opens a wine desktop that doesn’t open anything… aaaand then crashes.

I checked my stuff, and all my runtimes are up to date.

Thus spake Hawynh:

Whenever I click on the VASSAL.sh file, it opens a wine desktop that
doesn’t open anything… aaaand then crashes.

I checked my stuff, and all my runtimes are up to date.

What happens when you run this from the directory containing VASSAL.sh?

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


J.

The VASSAL.sh file shows something like this when I execute it and VASSAL dosn’t run.

#!/bin/sh

Execute this file to launch VASSAL on MacOS or Linux

Find where VASSAL is installed, dereferencing symlinks

INSTALL_DIR=$(dirname “$(readlink “$0” || echo “$0”)”)

Launch VASSSAL

cd “$INSTALL_DIR” && java -classpath lib/Vengine.jar VASSAL.launch.ModuleManager “$@”

But if I run your command VASSAL runs normally.

I have tried to modify the .sh to a new file with your command to no success.

Thanks for your time and dedication, Uckelman. :slight_smile:

Best regards

Raimon

Thus spake Raimonet:

The VASSAL.sh file shows something like this when I execute it and
VASSAL dosn’t run.

I don’t follow what you’re saying. What does “shows” mean here? Why
are you clicking on VASSAL.sh?

I suspect that the problem you’re having is that you’re inadvertantly
opening VASSAL.sh in a text editor rather than running VASSAL.sh.

But if I run your command VASSAL runs normally.

Good.

I have tried to modify the .sh to a new file with your command to no
success.

That’s not what I intended. The point of that command was to isolate
whether VASSAL itself runs—it’s not a suggested modification to
VASSAL.sh.


J.

Yes. I imagined that tour command tries to troubleshoot the problemas. The modificación of .sh das justo a try by miself.

I recovered the original .su after that. Now… what should I do next?

Thanks and sorry forma muy english. I hace not used it for almost twenty years

Raimon

Thus spake Raimonet:

Yes. I imagined that tour command tries to troubleshoot the problemas.
The modificación of .sh das justo a try by miself.

Ok.

I recovered the original .su after that. Now… what should I do
next?

Try running VASSAL.sh in a terminal from the directory where it’s
located. In your terminal:

cd /path/to/VASSAL
./VASSAL.sh

What happens then?

Thanks and sorry forma muy english. I hace not used it for almost twenty
years

Are you a native Spanish speaker? (I’m guessing that from your name and
the way you write.)


J.


messages mailing list
messages@vassalengine.org
vassalengine.org/mailman/listinfo/messages

Thus spake Raimonet:

Problem solved. It’s a problem with Ubuntu management of .sh files. It
opens them as text with Notepad instead of running the application. In
order to solve it, Nautilus has to be accessed and modified. I got
this by…

I’m glad you found a solution.

Are you a native Spanish speaker? (I’m guessing that from your name
and
the way you write.)

Well. In fact I am spanish-catalan speaker. The problem is that I
wrote the last message with my tablet and I didn’t realize that while
typing the message, the auto-complete option of the tablet was doing a
mess creating a nonsense half spanish-half english text.

No problem, I was just wondering.


J.