TurboVNC Client + MacOS 10.14.6 - JRELoadError

184 views
Skip to first unread message

Jafaruddin Lie

unread,
Apr 21, 2020, 1:14:44 AM4/21/20
to TurboVNC User Discussion/Support
Hi all
Got a simple question that I can't resolve (mainly since I don't have access to this mac).
So my user installed TurboVNC 2.2.4 via the dmg file.
Whenever we try to launch the client, we get JRELoadError and after checking, we're still running Java 1.6 that comes from Apple.
So we installed Java 1.8, can confirm this via the applet, and changed the .bash_profile to add the new java binary to the path (export PATH=/Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/:$PATH).
From the terminal, java -version is returning the latest version (build 1.8.0_251-b08) but we're still getting the JRELoadError after rebooting the computer.

My guess is that TurboVNC Client either can't find the correct path to the new binary, or still using the Java 1.6 installed.
How does the client look for the binary? Is there other variable I need to set?
Thank you in advance!

DRC

unread,
Apr 21, 2020, 11:47:19 PM4/21/20
to turbovn...@googlegroups.com
TurboVNC 2.1.2 was the last version that supported Java 1.6 on Mac (AKA
"Java for OS X Systems", which I tended to refer to as "Apple Java" to
distinguish it from "Oracle Java.") TurboVNC 2.2.x requires Oracle Java
or OpenJDK.

The Mac TurboVNC Viewer is ultimately looking for a file called
libjli.dylib. It first tries to execute /usr/libexec/java_home to get
the Java home directory, and if successful, the viewer looks for
libjli.dylib under {java_home}/jre/lib/jli/libjli.dylib, then
{java_home}/lib/jli/libjli.dylib, then {java_home}/lib/libjli.dylib. If
java_home doesn't return a sane value, then the viewer looks for
libjli.dylib under /Library/Internet
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/lib/jli/libjli.dylib. If
all of the above fail, then you get the infamous JRELoadError.

Hopefully that will help you troubleshoot what's going wrong.

TurboVNC 3.0 will have an embedded JRE, so it won't be necessary to futz
with Java anymore.

DRC

Jafaruddin Lie

unread,
Apr 22, 2020, 12:09:36 AM4/22/20
to turbovn...@googlegroups.com
Hi DRC
Thanks, that explains the issue.
The java_home returns 1.6, and it seems like we needed to either remove 1.6 or install 1.8 JDK.
All sorted now with your help, thanks!

--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/c84f0f51-e57e-21f8-56b9-c7d44976983a%40virtualgl.org.


--
Registered Linux user no. 384430

DRC

unread,
Apr 22, 2020, 12:15:23 AM4/22/20
to turbovn...@googlegroups.com

Correction:

I just looked at the code again, and the TurboVNC Viewer launcher will check the value of JAVA_HOME first before it tries to run /usr/libexec/java_home, so you should be able to set JAVA_HOME to the path of your Java 8 JRE.

Reply all
Reply to author
Forward
0 new messages