-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fiji fails to start Ubuntu after 2020 major update #258
Comments
This issue has been mentioned on Image.sc Forum. There might be relevant details there: |
Hey @JimageJ, so good that you found a workaround for the moment and shared it with us. Thanks! |
This issue has been mentioned on Image.sc Forum. There might be relevant details there: |
The workaround in in the Forum post does not work for me. |
@ctrueden identified an outdated scijava-common artifact that was shadowed by the N5 update site as the culprit of my issue and obsoleted the file on the update site. The above workaround works. |
I believe this is resolved in imagej/imagej-launcher#74 |
Hey folks,
I ran into problems getting the latest version to run on Ubuntu 20.04 after the update. I’ve got it working now but thought I’d post what my issue was, because it highlights a fault with the installation.
Ran the update and Fiji won’t start. Redownloaded the latest and it won’t start. The 2017 build starts fine, until I update it.
Running from the command line gives this:
Could not load Java library '/home/jim/Downloads/Fiji.app/java/linux-amd64/jdk1.8.0_172/jre//lib/server/libjvm.so': /home/jim/Downloads/Fiji.app/java/linux-amd64/jdk1.8.0_172/jre//lib/server/libjvm.so: cannot open shared object file: No such file or directory Warning: falling back to System JVM Could not launch system-wide Java (No such file or directory)
This made me realise that there is an issue with the Java the Fiji installs, so I’ve updated my Ubuntu Java installation and it now runs.
sudo apt install default-jre
(Crossposted on image.sc forum)
The text was updated successfully, but these errors were encountered: