Adamcake
commented
5 months ago 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 CWD on startup, but when Bolt starts its CWD will be somewhere in /opt.
The solution will be to add a "RuneLite (configure)" option to Bolt like the official launcher has. I'd already been meaning to do this but been wrapped up in something else recently.
A better workaround for now might be to set the jvm args you need in the _JAVA_OPTIONS environment variable.
On Tue, 30 Jan 2024, 15:22 Kyle Walters, @.***> wrote:
I am using Bolt on Arch Linux to play OSRS with RuneLite.
I have been troubleshooting an audio-related issue. This issue seems to be affecting some RuneLite Linux users. I found a solution to this issue mentioned here https://github.com/runelite/runelite/issues/3525#issuecomment-1813525702
I'm not very familiar with the inner workers on java relating to the --configure option that is mentioned in that solution. Although, I was able to confirm, that JVM options that are added via the java --configure option do not apply to instances of runelite that are started through the Bolt Launcher.
I suspect this is due to the fact the Bolt Launcher sets its own JAVA HOME, but unsure.
As I was able to confirm that adding those JVM options to the execution of the RuneLite.jar from outside of Bolt Launcher resolved the "no sound" issue for myself. As the JVM options applied via --configure did not apply to instances of RuneLite.jar that was launched through the Bolt Launcher, the temporary solution that I was able to implement is as follows.
- Execute java -jar RuneLite.jar --configure and add the following options to the JVM section:
-Djavax.sound.sampled.Clip=com.sun.media.sound.DirectAudioDeviceProvider -Djavax.sound.sampled.Port=com.sun.media.sound.PortMixerProvider -Djavax.sound.sampled.SourceDataLine=com.sun.media.sound.DirectAudioDeviceProvider -Djavax.sound.sampled.TargetDataLine=com.sun.media.sound.DirectAudioDeviceProvider
- Unmute the login screen music and see if this fixes the "no sound" issue, if it does, then proceed to the next steps.
- execute archlinux-java get and make note of the java version from the output.
- (as root) cd /usr/lib/jvm/
/bin - (as root) mv ./java ./java-real
- (as root) vim ./java and populate it with the following:
!/bin/bash
echo "$*" | grep -i "\ runelite.jar"
arguments=$(echo "$*" | sed "s/net.runelite.client.RuneLite//g")
if [ "$?" -eq 0 ]; then java2 $arguments -Djavax.sound.sampled.Clip=com.sun.media.sound.DirectAudioDeviceProvider -Djavax.sound.sampled.Port=com.sun.media.sound.PortMixerProvider -Djavax.sound.sampled.SourceDataLine=com.sun.media.sound.DirectAudioDeviceProvider -Djavax.sound.sampled.TargetDataLine=com.sun.media.sound.DirectAudioDeviceProvider net.runelite.client.RuneLite else java2 $* fi
7.(as root) chmod a+x ./java
- attempt launching RuneLite through the Bolt Launcher.
Notes: I recognize this solution isn't ideal for several reasons and should only function as a temporary "fix" until the downstream issue with alsa/java/runelite is resolved. Although its not an issue with Bolt Launcher itself, given the current working fix for this issue is a sub par solution, as you have to replace the java binary with a "helper" bash script that intercepts and modifies usage of the java command specifically when used for the RuneLite.jar. This can present issues as if java is updated, or you switch java versions, the solution will stop functioning, additionally, this solution may have an unidentified issue that leads to the execution of other java applications being affected.
With that in mind, below are the instructions for how to "undo" the changes.
(as root)
- cd /usr/lib/jvm/
/bin - mv ./java2 ./java
- chmod a+x ./java
and if you need to completely reinstall java, please refer to your distributions instructions for that matter.
— Reply to this email directly, view it on GitHub https://github.com/Adamcake/Bolt/issues/19, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHG6BIAZJ2UJNA5RXHRAJWLYREF43AVCNFSM6AAAAABCROHW42VHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYDQMJTGA2DOMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
deejcunningham
EspressoKyle
I am using Bolt on Arch Linux to play OSRS with RuneLite.
I have been troubleshooting an audio-related issue. This issue seems to be affecting some RuneLite Linux users. I found a solution to this issue mentioned here
I'm not very familiar with the inner workers on java relating to the --configure option that is mentioned in that solution. Although, I was able to confirm, that JVM options that are added via the java --configure option do not apply to instances of runelite that are started through the Bolt Launcher.
I suspect this is due to the fact the Bolt Launcher sets its own JAVA HOME, but unsure.
As I was able to confirm that adding those JVM options to the execution of the RuneLite.jar from outside of Bolt Launcher resolved the "no sound" issue for myself. As the JVM options applied via --configure did not apply to instances of RuneLite.jar that was launched through the Bolt Launcher, the temporary solution that I was able to implement is as follows.
java -jar RuneLite.jar --configureand add the following options to the JVM section:archlinux-java getand make note of the java version from the output.cd /usr/lib/jvm/<JAVA_VERSION>/binmv ./java ./java-realvim ./javaand populate it with the following:echo "$*" | grep -i "\ runelite.jar"
arguments=$(echo "$*" | sed "s/net.runelite.client.RuneLite//g")
if [ "$?" -eq 0 ]; then java-real $arguments -Djavax.sound.sampled.Clip=com.sun.media.sound.DirectAudioDeviceProvider -Djavax.sound.sampled.Port=com.sun.media.sound.PortMixerProvider -Djavax.sound.sampled.SourceDataLine=com.sun.media.sound.DirectAudioDeviceProvider -Djavax.sound.sampled.TargetDataLine=com.sun.media.sound.DirectAudioDeviceProvider net.runelite.client.RuneLite else java-real $* fi