Unfortunately, I do not have 10.5 nor 10.7 and I cannot reproduce with 10.6.

Would you be able to give me remote access with any of the two?

It appears that my test was not very thorough... I had a left-over jars/ij-launcher.jar file, and that actually fixed it.

So the problem was that the files from update/ were not moved in time for the ImageJ launcher trying to find jars/ij-launcher.jar (which will be called jars/ij-launcher-<version>.jar in the near future, hence the need to discover it). Instead of failing gracefully, it then tried to use the file name nevertheless (which was still uninitialised).

Now it moves the updated files earlier, and there is also some code to fail more gracefully should a similar issue crop up in the future.

The whole problem has been diagnosed with the help of Melissa Linkert.

Committed, pushed, uploaded and fixed!

I'm sorry to say that at my machine, the problem persists :(
(Mac OS 10.5, didn't test on 10.7 yet...)

A newly downloaded Fiji release (from fiji-macosx-20110307.dmg) updates once, tries to start up and now even reaches the splash screen and the stage where the Fiji dock icon changes to the Java coffee cup, but then quits silently.

Running fiji-macosx from within Fiji.app gives the following Terminal output (Segmentation fault is gone):

***
Kernel Information:  Darwin 9.8.0 i386
GNU bash, version 3.2.17(1)-release (i386-apple-darwin9.0)
Copyright (C) 2005 Free Software Foundation, Inc.
Uptime: /Users/eglinger/Desktop/Fiji.app/Contents/MacOS/fiji-macosx ; exit;
21:57  up 14 days, 22:17, 2 users, load averages: 1.81 1.53 1.45
Server time is: Wed May  9 21:57:20 CEST 2012
~ > /Users/eglinger/Desktop/Fiji.app/Contents/MacOS/fiji-macosx ; exit;
logout

[Process completed]
***

Jan

Is there any information in the Console (find it in Finder after clicking Go>Utilities)?

(In reply to comment #4)
> Is there any information in the Console (find it in Finder after clicking
> Go>Utilities)?
> 

I am also having this issue (Mac OS 10.6.8), even after attempting to automatically and then manually apply the fixes at http://fiji.sc/wiki/index.php/Fix_non-functional_Fiji_after_Update. I don't see any relevant entries in the console... Any other suggestions for how to get some useful debug information out of this?

Thanks!
-Nick

Nicholas, Jan, any chance you could let me into your system to investigate? We could use an SSH tunnel, if you're willing, please go to http://fiji.sc/IRC, log in (requires Javascript) and let me know, we'll take it from there.

Nicholas let me play with his Fiji installation and it seems as if my ImageJ launcher update from today "magically" solves the problems.

Jan: To fix your installation, please open the Terminal (in Finder's Go>Utilities) and change the directory to the path of your Fiji.app's Contents/MacOS. The following assumes that you installed Fiji to /Applications/ as suggested by the background image you see when double-clicking the .dmg file:

cd /Applications/Fiji.app/Contents/MacOS
curl -O http://jenkins.imagej.net/job/Stable-Fiji/ws/Fiji.app/Contents/MacOS/ImageJ-macosx
curl -O http://jenkins.imagej.net/job/Stable-Fiji/ws/Fiji.app/Contents/MacOS/ImageJ-tiger
chmod a+x ImageJ-*

After this, a double-click should open Fiji. Note that you will still see a flashing logo if another instance of Fiji is still running...