Skip to content

Commit 8d93355

Browse files
committed
Update installation troubleshooting directions
Attempt to cover the case where ImageJ.cfg is created intead of fiji.cfg
1 parent e151d0d commit 8d93355

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/ops/doc/Installation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,15 +33,15 @@ Double-check the `Fiji.app/config/jaunch` directory [Windows/Linux] or `Fiji.app
3333

3434
#### I did the new Java update but after restarting Fiji is not using Java 21
3535

36-
The new java should have been downloaded to `Fiji.app/java/[platform/` and will likely have a directory name along the lines of `zulu21[...]jdk21[...]`.
36+
In your `Fiji.app/config/jaunch` directory you should have a file named `fiji.cfg`. If this file is not present but you instead have an `ImageJ.cfg`, first try renaming `ImageJ.cfg → fiji.cfg` and launch Fiji again. This is a potential bug that can arise due to the switching of the launchers.
3737

38-
In your `Fiji.app/config/jaunch` directory you should have a file named `fiji.cfg` containing the line:
38+
If Java 21 is still not being used, look at the actual contents of the `fiji.cfg` file. This is a plain text file and can be edited in any text editor. It should be along the lines of:
3939

4040
```
4141
jvm.app-configured=/path/to/downloaded/java
4242
```
4343

44-
Ensure that the right hand side of this assignment matches the Java download location.
44+
The right-hand side of this assignment should be a path to the location where Java 21 was downloaded. It will be in the form of `Fiji.app/java/[platform/zulu21[...]jdk21[...]`. Ensure that this path is valid and correct.
4545

4646
#### Other failures
4747

0 commit comments

Comments
 (0)