#SpiralView 1.8.5 OpenJDK compatibility [linux ubuntu/pop_os 22.04]
1 messages · Page 1 of 1 (latest)
I might test/reproduce this behavior on default ubuntu distribution (22.04) to exclude any distribution fork-specific behavior, although I believe it uses same packages as the upstream
Have you tried any more recent jre?
Actually does spiralview even use systemwide java...
I don't think it does
Also I don't think you can run any SK related stuff natively with 64bit jre on linux (in the steam build though?)
I'm not certain
@fierce vale
How did it work on linux
It's spiralview but I'm wondering if anything is broken aside from steam login
I don't use the steam build
Doesn't matter, can you run it natively on 64bit jre?
The installer tries to find a system wide java 8 and makes a link to it, I'm pretty sure
Of course
Well, the client
Okay so that excludes both of my hypothesis
Haven't tried Spiralview
I could try later in a couple hours maybe
Sure
The initial "no such file or directory" sounds like something flatpak would be the cause of
Forgot that Spiral Knights use proton compatibility in order to run on linux, my bad. So, I installed the default steam .deb package from steam.com + default proton experimental. Same issues as above w/ openjdk 8 jre
Will try more recent jre, it seems 21 is current lts release
Just checked, it's present outside of flatpak installation. Makes me think it's something related to paths, as the only java folder I currently see is java_vm in the spiral knights local files
Installed lts release 21, same issue: 2024/09/03 20:04:56:993 SEVERE net.lucasallegri.spiralview: We have no compatible Java VM to work with, goodbye.
I might also try installing and running with Oracle HotSpot JRE implimentation, will report back
Ok, will check
If it still doesn't work install Knight launcher and try opening spiralview through it
1.6 reports that both 8 and 21 versions of jre are not compatible (openjdk ones)
Okay, will check, thank you!
Odd
Well, 21 would never work
@mighty relic what does no compatible java check exactly?
I think I had success running spiralview with 21
Or 17 at least
Yeah
Could it be an issue of using OpenJRE implimintation?
I'm sure running 17 with spiralview through KL works
spiralview requires a compatible java vm which means any 1.7 or 1.8, bear in mind that even if you start spiralview.jar through any java it does not mean it's using that to launch the editors
the spiralview "launcher" scouts for any valid java install in your machine and uses that
Is 1.8 akin to what openjdk8 is
Java versioning is confusing
I updated java through sudo update-java-alternatives --set, based on version outputted by --list, installed over apt, java -version updated immidiately
oh
I believe I know what the issue there is
the launcher checks for the version by checking if the version string explicitly contains "1.7" or "1.8", openjdk does not use that nomenclature and simply displays an "8" so it will not find it compatible even though it is
that does explain it
There were similar issues on linux with no compatible java error iirc
Yes. They mean the same thing
Ty
I'll push a fix for that in kl 2.0.4
could I send you the kl version with the fix and let me know if it does work now?
sure! I might need to check how spiralview shoud be launched from it
wait reading back on this, it did find openjdk8 compatible
checked for potential permission issues: -rwxrwxr-x 1 spiralview spiralview 25966175 Sep 3 20:28 ./KnightLauncher.jar*
the user-owner of ubuntu instance is spiralview, under him steam was installed
wait
why is there a java_vm folder aren't you on linux
that's for windows only
oh well you got it from steam
Did you install SK through proton compatibility layer
I guess that makes sense
delete the java_vm folder
so it doesn't detect it as windows
altho you'll have another issue and I believe this is the root of the problem
linux, yes, java_vm is there, although KnightLauncher asked me to patch java for 64x
if you're trying to start it from the steam version downloaded with proton
Okay
you wont have the .so files for lwjgl
cause it'll all be .dll
the ones in the native folder in sk's root directory I mean
Ohh, I think its because Spiral knights can be installed on linux only through proton, which is wine. There's .dlls in native folder
seeing how your sk root directory is inside a folder named spiralview I assume you only want this installation to toy with spiralview
I wonder if you can launch spiralview through proton
so I'd suggest downloading the standalone version and then using kl from there
I was very tempted to suggest that myself earlier lol
so, I put, for example, 1.6 SpiralView and then Knight Launcher will launch it?
nono my bad I didn't mean standalone spiralview
go to spiralknights.com and download the game from there
install it, and then put kl's jar within that installation
and it should be good to go
without SpiralView.jar?
yes when running spiralview through kl you don't need the spiralview.jar
it's already bundled within
understood, will install and check, although it might be tomorrow, is this okay?
no problem
ty, one more thing - knight launcher I should use one that is patched?
the one I sent here you mean?
yes
nope I just reverted the change as it wasn't anything to do with it
you can use 2.0.3
got it, appreciate the help!
no worries let me know if it works later
Well, I felt like I might as well. So I did.
It whines, but launches anyways.
let me add some logging to see where the issue is there
Isn't it the same issue as earlier?
shouldn't be, I saw this one before but I couldn't debug it
sec I'll dm you so the logs aren't public
Ok
Can confirm (thought registration would be needed to download sk from the site), with OpenJre 11 same notification is displayed for all 4 editors, which are launching successfully afterwards
the warning should be gone when 2.0.4 goes live in a bit
updated to 2.0.4, on Ubuntu 22.04, SK standalone instance: warning disappeared, attaching log, might be of use as on pop_os 22.04 (not a point of nitpicking, just noticed same error in it's log), a standalone SK instance: warning persisted.
the one you attached is the log on pop os?
no, it's one from ubuntu
send me the one from pop os so I can take a look
OS's names in logs' filenames
Regarding ubuntu log: spiralview@spiralview-Standard-PC-Q35-ICH9-2009:~/spiral$ file java/bin/jar java/bin/jar: cannot open 'java/bin/jar' (No such file or directory) - the searched jar seem to be abscent
the warning I see on pop os isn't an issue, java 11 is indeed non compatible
my bad, have not reverted to version 8. Now reselected java 8 - no notification is displayed.
this is also a non issue since kl doesn't need that file nowadays it's from a deprecated feature. I suspect it's not erroring because it doesn't have permissions to that file but because it cannot extract it to that location hence why it's not present
understood, ok, reported as just saw it
there's also some null pointer exceptions in both logs files which I know why are occurring and should be fixed next update
but they shouldn't break the launcher nonetheless
yes, editors do launch fine
great to hear
just tested steam version for linux, seems that it is detected as windows
1 moment, i'll attach logs
I believe the steam one is always windows regardless if you have proton enabled or not
cause there's no linux version of it
only windows and mac
I suppose, Steam offers no native linux build, Sk can be installed only over proton, and as seen above, it is, if i understood correctly, windows build then is identifiable by .dlls
there KL crashes with the log above
this is same SK installation from Steam where java_vm was removed
please note, this is not an issue for me, only testing wherein it is appropriate in a current context
I see. this should be normal behavior too, java_vm would never be missing from the steam install in a normal scenario
at first I thought you had it for some other reason that's why I asked for it to be removed
ok, I can reinstall Steam's SK and test KL there
I assume kl will launch but the game won't since it won't be able to execute java.exe to launch the game for obvious reasons
same error as above, with java_vm, yeah
for behavior reproduction, it's ubuntu 22.04.4 LTS desktop, installer was run with default settings. Very gratefull for 2.0.4 release
Is the issue solved then?
I would consider it solved, yes
Thanks