Fleet not starting under ubuntu 22.04
Answered
I tried running Fleet under ubuntu 22.04 and no matter how i try to start it nothing happens.
Before that i was running Ubuntu 20.04 and there where no problems.
After fresh install of the Ubuntu fleet does not start under X11 session or Wayland.
Starting with -d does not output anything.
Tried running the directly the bin:
JetBrains/Toolbox/apps/Fleet/ch-0/1.10.192/bin/Fleet
but this fails with :
Error: could not find libjava.so
Error: Could not find Java SE Runtime Environment.
Please sign in to leave a comment.
may be you should install openjdk or other java environment
I tried with both openjdk and oracle 17
Starting from the JetBrains Toolbox dies silently.
I tried running the binary directly even with several versions of the JDK but the result is the same.
$ java --version
java 19.0.1 2022-10-18
Java(TM) SE Runtime Environment (build 19.0.1+10-21)
Java HotSpot(TM) 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
$ echo $JAVA_HOME
/usr/lib/jvm/jdk-19
$ ./bin/JetBrains/Toolbox/apps/Fleet/ch-0/1.12.97/bin/Fleet
Error: could not find libjava.so
Error: Could not find Java SE Runtime Environment.
Could you run Fleet from command line with strace and post the output?
Btw, try to use any other (than bin) installation directory location for the Toolbox App and for Fleet (see how to change install location for Fleet here). In case the issue is similar to this one.
Hmm the way Fleet searches for libjava.so is this:
So i tried to symlink it to my $JAVA_HOME for testing.
Then ran the strace again
And still its not starting
Have you tried moving installation into a different directory?
Please file an issue at https://youtrack.jetbrains.com/issues/FL with the provided information.
Re-Installed it and nothing improved but i tried linking the runtimelib from Fleet dir
Because when run with strace at the end it searched
Now its starts through the shortcut or the terminal...
We have found an issue in some other product with similar symptoms https://github.com/JabRef/jabref/issues/5591
It looks like there's a jpackage bug that prevents apps from starting if they are located in a bin directory.
It should help to change the name of ~/bin directory into something else (or install Fleet in another directory).
This is jlink Java bug https://bugs.openjdk.org/browse/JDK-8219962 We will try to come up with the workaround by showing a notification to the user. Until we stop using jlink.