Create account / Log in

3.2.0-beta3 Does Not Work on OSX.

Issues with the Vassal engine.

Moderators: Tim M, uckelman

3.2.0-beta3 Does Not Work on OSX.

Postby Howitzer99 » September 28th, 2012, 5:37 am

Hi All,

Myself and several others have discovered that 3.2.0-beta3 is broken on OSX, specifically versions 10.7.4 and 10.8.2 (so far). I've posted a message on BGG regarding this, and am re-posting it here so that the right people get the information.

I've tried using the newest beta version on OSX 10.7.4, but it will not start. The Vassal icon just bounced in the dock, and never launches. Clicking the icon to raise the application causes it to close.

Can someone confirm that this version is actually working on OSX? Previous version have never acted this way, even the previous 3.2.0-beta2 launches correctly.


Thanks,
Dave
Howitzer99
 
Posts: 13
Joined: November 30th, 2011, 4:20 am

Re: 3.2.0-beta3 Does Not Work on OSX.

Postby tar » September 28th, 2012, 8:14 am

On Thu, Sep 27, 2012 at 10:37 PM, Howitzer99 wrote:

> Hi All,
>
> Myself and several others have discovered that 3.2.0-beta3 is broken on
> OSX, specifically versions 10.7.4 and 10.8.2 (so far). I've posted a
> message on BGG regarding this, and am re-posting it here so that the
> right people get the information.
>
> I've tried using the newest beta version on OSX 10.7.4, but it will not
> start. The Vassal icon just bounced in the dock, and never launches.
> Clicking the icon to raise the application causes it to close.
>

For some reason, the application has not been built correctly.
In particular, the JavaApplicationStub is not set to be executable.
Launching then fails with a permission denied error.

9/28/12 1:08:02.078 AM com.apple.launchd.peruser.501:
([0x0-0x9a09a].org.vassalengine.VASSAL[2768])
posix_spawn("/Volumes/VASSAL-3.2.0-beta3/VASSAL-3.2.0-beta3.app/Contents/MacOS/JavaApplicationStub",
...): Permission denied

Manually changing the permissions to be executable fixes the problem.
User avatar
tar
 
Posts: 772
Joined: January 2nd, 2008, 6:53 pm
Location: Los Angeles area

Re: 3.2.0-beta3 Does Not Work on OSX.

Postby uckelman » September 28th, 2012, 9:28 am

Thus spake tar:
> [This message has been edited.]
>
> On Thu, Sep 27, 2012 at 10:37 PM, Howitzer99 wrote:
>
> > Hi All,
> >
> > Myself and several others have discovered that 3.2.0-beta3 is broken
> on
> > OSX, specifically versions 10.7.4 and 10.8.2 (so far). I've posted a
> > message on BGG regarding this, and am re-posting it here so that the
> > right people get the information.
> >
> > I've tried using the newest beta version on OSX 10.7.4, but it will
> not
> > start. The Vassal icon just bounced in the dock, and never launches.
> > Clicking the icon to raise the application causes it to close.
> >
>
> For some reason, the application has not been built correctly.
> In particular, the JavaApplicationStub is not set to be executable.
> Launching then fails with a permission denied error.
>
> 9/28/12 1:08:02.078 AM com.apple.launchd.peruser.501:
> ([0x0-0x9a09a].org.vassalengine.VASSAL[2768])
> posix_spawn("/Volumes/VASSAL-3.2.0-beta3/VASSAL-3.2.0-beta3.app/Contents/MacO
> S/JavaApplicationStub",
> ...): Permission denied
>
> Manually changing the permissions to be executable fixes the problem.
>

The bad file permisions were caused by the fix for Bug 4807. Try build
3.2.0-svn8382:

http://www.vassalengine.org/~uckelman/builds/

If this works, let me know and I'll replace the 3.2.0-beta3 builds with
it.

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

Re: 3.2.0-beta3 Does Not Work on OSX.

Postby uckelman » September 28th, 2012, 7:52 pm

I've replaced the 3.2.0-beta3 builds on SF with ones with correct file permissions. Try now.
User avatar
uckelman
Site Admin
 
Posts: 8137
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: 3.2.0-beta3 Does Not Work on OSX.

Postby tar » October 1st, 2012, 2:56 pm

The application now launches correctly.

Unfortunately, I'm having problems with the display of the tiled images.
Still looking into that, but I have to go to work now.

BTW, Apple has now made other things more difficult (starting with Lion) by hiding the user's Library folder. This will make finding the errorLog file harder. I plan to update the Vassal module user FAQ to address this issue. I also want to put in an entry that explains where to find the errorLog. But I need to get that information for the various operating systems.
WAIT: I see that the Help menu now shows the errorLog (since which version?), making finding it generally less important. I suppose I should add a FAQ entry anyway, for diagnosing those cases where Vassal doesn't start up at all.
User avatar
tar
 
Posts: 772
Joined: January 2nd, 2008, 6:53 pm
Location: Los Angeles area

Re: 3.2.0-beta3 Does Not Work on OSX.

Postby tar » October 4th, 2012, 4:39 am

Re: Tiled images in Mac OS X 3.2.0-beta 3

I found that I could get tiled map images to work by disabling Quartz rendering in the main Vassal preferences. (Not the module preferences).
User avatar
tar
 
Posts: 772
Joined: January 2nd, 2008, 6:53 pm
Location: Los Angeles area

Re: 3.2.0-beta3 Does Not Work on OSX.

Postby uckelman » November 20th, 2012, 8:54 pm

Thus spake tar:
> Re: Tiled images in Mac OS X 3.2.0-beta 3
>
> I found that I could get tiled map images to work by disabling Quartz
> rendering in the main Vassal preferences. (Not the module preferences).
>

Follow-up: The options for Quartz rendering has been removed in
3.2.0-svn8428.

Thanks for noticing this problem.

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8137
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 1 guest