• Editor
  • OS X 1.1.0 won't launch - here's a fix.

Related Discussions
...

Then use the command I posted to run it. :think:

java -server -jar /Applications/Spine/Spine.app/Contents/MacOS/launcher/launcher-full.jar

Well, I made it a little easier to use an alternate Java. If you define an environment variable called SPINE_JAVA, it will use that when Spine.app is run. To use the system Java, you'd set it to "java" (without quotes). Eg, from the command line...

export SPINE_JAVA=java
open Spine.app

There are various ways to set environment variables in OS X:
http://stackoverflow.com/questions/1356 ... es-in-os-x
You can use the RCEnvironment tool if you want a GUI for doing it:
http://www.rubicode.com/Software/Bundle ... nvironment

Thanks Nate. That's a cleaner solution, and one that I'm happy with.

Sorry Nate - I've added the environment variable (using the GUI tool you linked to), but I'm still getting the X11 prompt. I've rebooted, just to be sure the variable was active.

I'm running Spine v1.1.0.7, in OSX 10.8.2.

Any ideas?

Hmm. If you open the Console app, do you see a message from Spine when it starts? It should say "Spine: Using Java: xxx" where xxx is the SPINE_JAVA you set. What happens if you try:

export SPINE_JAVA=java
open /Applications/Spine.app

If that doesn't work, then I don't think you have the latest Spine launcher, you should download it again. If that works then it means however you are launching Spine isn't seeing your environment variable. I've read that launching via Spotlight may not see your variable:
http://www.digitaledgesw.com/node/31

I'm definitely running the latest build (I just re-installed to be sure).

Even when I run those commands, I'm still presented with the X11 prompt. Weird.

I can see the SPINE_JAVA entry in my exports:

...
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SPINE_JAVA="java"
declare -x SSH_AUTH_SOCK="/tmp/launch-65LXli/Listeners"
declare -x TERM="xterm-256color"
...
Nate wrote

If you open the Console app, do you see a message from Spine when it starts? It should say "Spine: Using Java: xxx" where xxx is the SPINE_JAVA you set.

^
|

If you just want to get it working, you can right click Spine.app, Show Package Contents, expand Contents/MacOS, and edit run.sh with TextEdit. Where it says:

"$SPINE_JAVA" \

Check that to:

java \
Nate wrote

If you open the Console app, do you see a message from Spine when it starts? It should say "Spine: Using Java: xxx" where xxx is the SPINE_JAVA you set.

I didn't understand what you meant by "console". Are you referring to terminal? If so, I don't see that text, no.

By Console app I mean an app that comes with OSX called Console. You can find it by clicking Spotlight (the magnifying glass in the upper right of the screen) and typing console.

However, I found a problem in another thread... the builds I've been pushing don't actually have the changes they should. If you could please download the launcher again, I think you'll find it works. Sorry about this mess! :bang:

  • 編集済み

Sorry Nate - I'm still getting the X11 prompt, and nothing appears in the console window when I run the app.

This is what I see when I launch via the java command:

Spine Launcher 1.0.08-full
Mac OS X x86_64 10.8.2
Java 1.6.0_43 Apple Inc.
Java HotSpot(TM) 64-Bit Server VM
Up to date: 1.1.07
Spine 1.1.07-full
ATI Technologies Inc.
ATI Radeon HD 5750 OpenGL Engine
2.1 ATI-1.0.29
Started.

Well, at least my Spine stuff is doing the right thing. 🙂 Your logs show that it's using "Java 1.6.0_43 Apple Inc.". That is your system Java installation, not the Java bundled with Spine (which would say "OpenJDK unofficial"), so it is using the environment variable. Nothing in Spine shows that X11 popup, and you aren't using the Java bundled with Spine so I guess even the Apple Java is requiring X11, doesn't look like there is a way around it. I know you said that Spine used to run without X11, but I'm not sure how that is possible. Maybe you did a system update and Apple changed things? Maybe you started using a different system Java? You can choose which system Java to use by opening Java Preferences (use Spotlight, the magnifiying glass in the upper right of the screen, to find it).

The trial and the initial, post-Kickstart campaign releases worked just fine on my system. I'm still using the same system, so I can only assume that the recent Apple Java update changed something? I dont know.

I've never seen X11 be required in any Java interaction on OS X.

I can try to take a look on my system a bit later and see if I can reproduce the issue with the latest installer.

terrymisu wrote

I've never seen X11 be required in any Java interaction on OS X.

I can try to take a look on my system a bit later and see if I can reproduce the issue with the latest installer.

In fact, it should be mentioned that X11 is no longer maintained by Apple. It's all now here.

Do you have an old version of X11? It might be a good idea to grab the latest XQuartz build and install that, just to make sure it's not some weird interaction.

That said, I don't see how Apple could be requiring Java to interact with components that aren't bundled with the OS anymore... seems mysterious indeed.

Here's an official Apple Support KB about it: http://support.apple.com/kb/HT5293

Apple no longer maintains Java for OSX. In a recent update, Apple has removed Java 6 (formerly maintained by Apple) and replaced it with Java 7 (maintained by OpenJDK).

Nate wrote

Apple no longer maintains Java for OSX. In a recent update, Apple has removed Java 6 (formerly maintained by Apple) and replaced it with Java 7 (maintained by OpenJDK).

1.6 is still being actively maintained by Apple in terms of security patches and whatnot for 10.8.x.

I think the OS will now redirect to the Oracle stuff for systems that don't have Java installed, but I haven't verified this.

So it's a bit of a mixed bag at the moment... unfortunately.