Karakun Support Forums

pi@pi:~ $ which javaws
/usr/local/bin/javaws
pi@pi:~ $ ls -al /usr/local/bin/javaws
lrwxrwxrwx 1 root root 24 Feb 11 11:32 /usr/local/bin/javaws -> /opt/OpenWebStart/javaws
pi@pi:~ $ javaws -version
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be 1.8 ...

Just out of curiosity. The OWS installer comes with a bundled 64bit JRE. How are you running this on a 32bit Linux??

Beats me how it runs at all, but it turns out that the 32bit aspect is irrelevant. It does the same in a 64b environment

pi@pi:~/Desktop $ javaws https://boardspace.net/java ...

That wouldn't be very satisfactory even if it worked, which it doesn't. Not satisfactory
because it's a public URL, and it would exclude people who are running newer versions
of java. But it doesn't work:

~/Desktop $ javaws https://boardspace.net/java/boardspacepi.jnlp
No suitable Java Virtual ...

Note that this is on a different host from my other (similar) bug reports. This one
is a x64 raspberri pi. but this seems to be a different problem.

pi@pi:~/Desktop $ javaws boardspace7.jnlp
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be 1.8.
Please ...

Yes.

I have a suspicion the problem is a "command line too long" type - not in java but somewhere
in the connective tissue..

same result

launching with the full path fixes this problem.

similarly, launching directly form a web url doesn't work, but in a different way.

ddyer@kali:~/Downloads$ javaws https://boardspace.net/java/boardspace7.jnlp
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
[ITW-CORE][2021-01-10 01:32:53.331 PST][INFO ][com ...

Openwebstart doesn't quite work in this configuration, installed on an x86 linux machine. The same jnlp
launches fine on windows and mac.

In this case, the jnlp was downloaded to the user Downloads folder. Clicking to launch just seems to fizzle,
but launching from a shell shows this:


dyer@kali ...