⚠

NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 130 - fiji-linux64 doesn't launch
fiji-linux64 doesn't launch
Status: RESOLVED REMIND
Product: Fiji
Classification: Unclassified
Component: Other
unspecified
PC Linux
: P2 blocker
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2010-01-14 22:06 CST by Albert Cardona
Modified: 2010-01-15 15:34 CST
1 user (show)

See Also:
Description Albert Cardona 2010-01-14 22:06:56 CST 
Download fiji pilsen, and extract the archive.

Double-click the fiji-linux64 executable: nothing happens.

In a terminal, when run:

$ ./fiji-linux64
Could not find fiji.Main

(or a very similar message regarding fiji.Main)

When ./fiji --dry-run, all looks ok.
When copy-pasting the dry-run output and preppending the path the java/linux-amd64/jdk.../java , then fiji runs without any problem.

How can I triage this bug in this linux machine?
Comment 1 Jean-Yves Tinevez 2010-01-15 08:59:06 CST 
(In reply to comment #0)

I can't reproduce the bug on a linux CentOS machine. 
Fiji launches ok with no error.
Maybe it is linked to the java installation on your machine?
Comment 2 Albert Cardona 2010-01-15 11:28:03 CST 
This error is real. The java used is that of the Fiji installation.
The error does not seem to be related to the java install.

What I would like is hints on how to track what is really happening. Can the fiji executable told to me more verbose, for example?

I will try these:

--java-home <path>
	specify JAVA_HOME explicitly
--print-java-home
	print Fiji's idea of JAVA_HOME
--print-fiji-dir
	print where Fiji thinks it is located


... and see where I get.
Comment 3 Albert Cardona 2010-01-15 12:53:56 CST 
After further inspection, this is the usual: JAVA_HOME was set to /usr/lib64/jvm/jre

Launching fiji like:

./fiji-linux64 --java-home java/linux-amd64/jdk1.6.0_16

... solves the problem.

So is this that fiji prefers the JAVA_HOME to its own?

If so, the error message when failing to launch should be more explicit. Instead of "Could not find fiji.Main", it should say: "Using JAVA_HOME=/so/and/so, then Could not find fiji.Main. You may want to try using fiji's bundled java by launching with ./fiji-linux64 --java-home java/linux-amd64/jdk1.6.0_16"

Now that would be excellent.
Comment 4 Johannes Schindelin 2010-01-15 14:07:14 CST 
The problem is that it _should_ work even with JAVA_HOME set to a valid JRE.  Is the JRE on your computer maybe a 32-bit one?  What does the launcher say if you add the --dry-run option (in particular, does the classpath contain the correct Fiji.jar path)?
Comment 5 Albert Cardona 2010-01-15 15:34:52 CST 
Yes, misc/Fiji.jar is in the class path. I couldn't see anything wrong--other than Fiji itself being "old", i.e. Fiji Pilsen.