"VASSAL-3.2.8" is damaged and can't be opened.

I’m trying to install Vassal and I’m getting the error message in the title, plus it telling me to eject the disk image, every time I try to open it from the disk image. I read the release notes and tried opening it by right-clicking and hitting “open” from the menu there but I get the same issue.

I’m on OSX 10.9 (Mavericks), and I’m not amazing with computers, so a simple fix would be appreciated :stuck_out_tongue:.

Model: Macbook Pro
OS: OSX 10.9
CPU: don’t know
Memory: 4GB
Video: don’t know
VASSAL: 3.2.8
Java: don’t know, I think 1.6-something

Thus spake MandalorynOranj:

I’m trying to install Vassal and I’m getting the error message in the
title, plus it telling me to eject the disk image, every time I try to
open it from the disk image. I read the release notes and tried opening
it by right-clicking and hitting “open” from the menu there but I get
the same issue.

I’m on OSX 10.9 (Mavericks), and I’m not amazing with computers, so a
simple fix would be appreciated :stuck_out_tongue:.

Have you checked whether you actually have a corrupt download? You can
do that from the command line with md5sum and sha1sum. You should get
an MD5 of 375638b9d35b437597d0b0ce4991cf3a and an SHA1 of
aaaa237bde7562a33dd34eee1e84cfb61310ece7. Please verify this before we
continue troubleshooting.


J.

Ok I just checked those and they came out the same as what you posted.

The simple answer is to run it properly – copy it from the dmg to /Applications first. I’ve found that it doesn’t always work as expected if you try to run it straight from the dmg because Java wants to modify the bundle for some reason.

Assuming that dragging it from the dmg into my Applications folder is the same as that, I’ve tried it, and it still says it’s damaged and then advises me to move it to the Trash.

I’m going to bump this, but also some useful info: I’ve updated to the latest version of Java for OSX, and the problem hasn’t changed.

I would run permissions and disk checks from Disk Utility to make sure that everything is working properly in the OS. Eject and then re-mount the dmg and try copying it over again after those two repairs complete.

Maybe also check whether you can run the app bundle from the command line using ‘open’.

Still no luck. Tried all of those suggestions, plus repairing the disk image itself in Disk Utility, nothing changes.

Thus spake MandalorynOranj:

Still no luck. Tried all of those suggestions, plus repairing the disk
image itself in Disk Utility, nothing changes.

What happened when you tried running the app bundle using open from
the command line? (What precisely did you type? What effects did you
observe?)


J.

I typed "open " and then dragged the icon from the disk image into the Terminal to add its path.

This is what came up when I hit Enter:
(I couldn’t get the image embed to work, so here’s a Photobucket link http://s1092.photobucket.com/user/MandalorynOranj/media/ScreenShot2013-12-04at93946AM.png.html?sort=3&o=0)

Thus spake MandalorynOranj:

I typed "open " and then dragged the icon from the disk image into the
Terminal to add its path.

This is what came up when I hit Enter:
(I couldn’t get the image embed to work, so here’s a Photobucket link
s1092.photobucket.com/user/Manda … sort=3&o=0)

This isn’t what I asked for. I need to see the exact command you had
in the terminal.


J.

Sorry, misinterpreted you.

open /Volumes/VASSAL-3.2.8/VASSAL-3.2.8.app

Thus spake MandalorynOranj:

Sorry, misinterpreted you.

open /Volumes/VASSAL-3.2.8/VASSAL-3.2.8.app

Ok.

  • Is /Volumes/VASSAL-3.2.8/ where VASSAL-3.2.8.app is?

  • Is there any output in the terminal when you run this command?


J.

I think so, that’s the path that appears when I drag the icon from the DMG into Terminal. It doesn’t give me an output in the Terminal, it acts the same as if I tried to open it from the DMG. When I move it into Applications and redo it (with the command becoming open /Applications/VASSAL-3.2.8.app) the same thing happens, no output and reacting the same as if I tried to open it directly.

Again, sorry if I’m not getting this, I don’t know a whole lot about working with the Terminal. Thanks so much for helping me and being patient though, I really appreciate it.

Thus spake MandalorynOranj:

I think so, that’s the path that appears when I drag the icon from the
DMG into Terminal. It doesn’t give me an output in the Terminal, it acts
the same as if I tried to open it from the DMG. When I move it into
Applications and redo it (with the command becoming open
/Applications/VASSAL-3.2.8.app) the same thing happens, no output and
reacting the same as if I tried to open it directly.

Again, sorry if I’m not getting this, I don’t know a whole lot about
working with the Terminal. Thanks so much for helping me and being
patient though, I really appreciate it.

Please come to the #vassal IRC channel so we can troubleshoot this in
realtime:

vassalengine.org/irc.php

There’s usually someone around who knows Macs. Please stick around until
you get a reply, as might take a while for us to respond initially.


J.

Solution to the problem: in System Preferences → Security & Privacy, make sure “Allow apps downloaded from:” is set to “Anywhere.” This will allow it to run.

For future reference:
/Volumes/VASSAL-3.2.8/VASSAL-3.2.8.app

is what one would expect for the path when the Vassal app is in the mounted
.dmg image.
So this is being opened from the read-only mounted disk image.

On Wed, Dec 4, 2013 at 8:42 AM, Joel Uckelman uckelman@nomic.net wrote:

Thus spake MandalorynOranj:

Sorry, misinterpreted you.

open /Volumes/VASSAL-3.2.8/VASSAL-3.2.8.app

Ok.

  • Is /Volumes/VASSAL-3.2.8/ where VASSAL-3.2.8.app is?

  • Is there any output in the terminal when you run this command?


J.


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