Adam
Adam
There's no easy way for Bolt to check this unfortunately. I'd have to do a load of PATH searching which would noticeably slow down the launch. I think I'll just...
I talked to the runelite devs about this recently. The reason --configure doesn't work is because it saves a settings.json in the CWD, and runelite searches for that file in...
An extra wrinkle in this situation is that runelite.jar is actually just a launcher, which downloads all the latest runelite binaries and runs them by starting up a totally separate...
Bolt version 0.8.2 is out on AUR and has a "Configure RuneLite" launch option which launches with --configure. I'd appreciate one of you confirming that it works correctly.
Regarding your helper script, command 2 is definitely the parent process spawning the child process. So your helper script is intercepting that somehow.
That's the same issue as #12. I should really add this to the readme.
Please confirm this issue still happens after setting PULSE_RUNTIME_PATH as described in #12?
All of this family of issues should be fixed absolutely for good in 0.9.
I haven't heard of that before. You said you installed the RuneLite package directly from AUR to fix the issue - is it possible that this also installed a dependency...
Well there you go then. It is documented in optdepends as `'jre17-openjdk: runelite/hdos'` (although incidentally you can use any Java version.) I think it would print something to stderr too.