Bliss won't start on a Mac

[vsperez78]

Hello.

I purchased Bliss back in May 2010. It worked fine for the first month. My wife and I haven't tried using it since then. However this past weekend when trying to open it it will not start. It just bounces on the dock and then disappears. This is the same computer it worked on before. All software is up to date. I'm using an intel MacBook Pro.

Any suggestions?

Thanks!

[Don]

I would first make sure you have jBliss 1.6 which was released since you bought Bliss. Also make sure your Mac has Java installed and running.

Assuming it still doesn't work, you might want to look at the Mac Console and see if there are any messages.

Don

[Xenon]

I am having the same problem ... it seems to start, and then just shuts down ...

messages from Console:
12/23/10 6:56:27 PM [0x0-0x22d22d].Bliss[10013] [JavaAppLauncher Warning] Java application launched from PPC or bad stub. Relaunching in 32-bit, and tagging sub-processes to prefer 32-bit with $JAVA_ARCH=i386.
12/23/10 6:56:27 PM [0x0-0x22d22d].Bliss[10013] [LaunchRunner Error] The main class "com.GamesForLoving.Bliss.BoardBase" could not be found.
12/23/10 6:56:27 PM [0x0-0x22d22d].Bliss[10013] [JavaAppLauncher Error] CallStaticVoidMethod() threw an exception
12/23/10 6:56:27 PM [0x0-0x22d22d].Bliss[10013] Exception in thread "main" java.lang.NullPointerException
12/23/10 6:56:27 PM [0x0-0x22d22d].Bliss[10013] at apple.launcher.LaunchRunner.run(LaunchRunner.java:112)
12/23/10 6:56:27 PM [0x0-0x22d22d].Bliss[10013] at apple.launcher.LaunchRunner.callMain(LaunchRunner.java:50)
12/23/10 6:56:27 PM [0x0-0x22d22d].Bliss[10013] at apple.launcher.JavaApplicationLauncher.launch(JavaApplicationLauncher.java:52)
12/23/10 6:56:27 PM com.apple.launchd[9253] ([0x0-0x22d22d].Bliss[10013]) Exited with exit code: 1
12/23/10 6:56:28 PM [0x0-0x22e22e].Bliss[10014] [JavaAppLauncher Warning] Java application launched from PPC or bad stub. Relaunching in 32-bit, and tagging sub-processes to prefer 32-bit with $JAVA_ARCH=i386.
12/23/10 6:56:28 PM [0x0-0x22e22e].Bliss[10014] [LaunchRunner Error] The main class "com.GamesForLoving.Bliss.BoardBase" could not be found.
12/23/10 6:56:28 PM [0x0-0x22e22e].Bliss[10014] [JavaAppLauncher Error] CallStaticVoidMethod() threw an exception
12/23/10 6:56:28 PM [0x0-0x22e22e].Bliss[10014] Exception in thread "main" java.lang.NullPointerException
12/23/10 6:56:28 PM [0x0-0x22e22e].Bliss[10014] at apple.launcher.LaunchRunner.run(LaunchRunner.java:112)
12/23/10 6:56:28 PM [0x0-0x22e22e].Bliss[10014] at apple.launcher.LaunchRunner.callMain(LaunchRunner.java:50)
12/23/10 6:56:28 PM [0x0-0x22e22e].Bliss[10014] at apple.launcher.JavaApplicationLauncher.launch(JavaApplicationLauncher.java:52)
12/23/10 6:56:28 PM com.apple.launchd[9253] ([0x0-0x22e22e].Bliss[10014]) Exited with exit code: 1

Any ideas .....

[Xenon]

Ok,

I have J2SE 6.0 selected as the top priority, and jBliss (for linux) will run, but jBliss (for mac) will not run.

Is it a difference between PPC and Intel Macs, and differences in the J2SE for different chipsets?

[Xenon]

While Searching on line ... I came up with this. I've seen several posts very similar on several boards. It seems that the Apple launcher cares about 32 bit or 64 bit ....

This is part of a change to the double-clickable app launching policy (which we explained in detail in the developer preview release notes). To enabled the Finder's "Run in 32-bit mode" checkbox for Java apps, and to make the transition to 64-bit by default easier, we've modified the JavaApplicationLauncher.framework to only launch application's in the architectures they have present in their JavaApplicationStub.

This was done now for a variety of reasons: until Update 4, the JavaApplicationStub and all apps that were bundled with it were 32-bit Universal. Very few apps required 1.6 in their Info.plist, so now was the best time to switch this policy. Applications with PPC or PPC/i386 stubs would continue to run in 32-bit mode indefinitely, until they rebundled after Update 4, which would then opt them into launching 64- bit (with the ability to downshift to 32-bit using the checkbox Finder's Get Info window). This simplifies the rule down to "if you don't have the architecture present, we won't launch you in it", which is exactly the same rule for launching native Cocoa apps.

The thinking is that if you haven't rebundled, you likely haven't ever considered that you'd be run in 64-bit mode (and when users have dragged Java SE 6 to the top of their Java Preferences, they found that some of their applications stopped working). By preventing apps from being launched in 64-bit if they haven't rebundled, we can maintain the widest compatibility, with a minor impact on developers (and actually let them have a say in what their version and architecture requirements are).

In your case, since you are manually modifying the Info.plist to 1.6+, replacing the JavaApplicationStub is also required, since IntelliJ 7 was likely not expecting to be launched in 64-bit, and may contain some 32-bit only native libraries.

Hope this explains what you are seeing,
Mike Swingler
Java Runtime Engineer
Apple Inc.

Hope this helps ...

Xenon

[wworsham]

Having the same problem

[Sarcas]

Had some similar problems, but at this moment Bliss does start up. I do see an error in the console:

Code: Select all

21-04-11 09:29:38   [0x0-0x98098].Bliss[8711]   [JavaAppLauncher Warning] Java application launched from PPC or bad stub. Relaunching in 32-bit, and tagging sub-processes to prefer 32-bit with $JAVA_ARCH=i386.

Also I have found that my anti-virus app (Sophos, free Mac version) really slows down launching Bliss. I have listed Bliss now in the 'exclude' section, and now it launches fine.

S.

[wworsham]

I was able to correct the error by downloading the latest java directly from the Apple website. Software Update said I was up to date, but I found an update on the site any way. Once I installed it everything worked fine.

http://support.apple.com/kb/DL1360

[Sarcas]

Just checked (here), I do have the latest version of Java installed. But as I said, it does start up, albeit with an error in the console.

S.

[Don]

Check this thread, there are a couple of things there that might help.

http://www.gamesforloving.com/forum/viewtopic.php?f=2&t=1052

Don

[Sarcas]

Ah, I overlooked that thread. Replacing JavaApplicationStub solves the error indeed, thanks.

S>