[BUG]: Absolute InfoSoundName paths even in AppImage version

[llsant]

Describe the Bug

PCSX2, on the first time run, sets the default .wav file paths for sounds related to the achievements feature. The user is allowed to pick other files on the system. However, the default paths for InfoSoundName, UnlockSoundName and LBSubmitSoundName point, respectively, to

{appimage runtime dir}/usr/bin/resources/sounds/achievements/message.wav

{appimage runtime dir}/usr/bin/resources/sounds/achievements/unlock.wav

{appimage runtime dir}/usr/bin/resources/sounds/achievements/lbsubmit.wav

However, take into account that for AppImage packs, the AppImage runtime will create a usermode mount point under /tmp/._some_random_stuff to mount the bundled squashfs with PCSX2, libraries, assets and so on. But the AppImage version is not meant to be portable, it (rightfully) stores configuration under $HOME/.config/PCSX2.

Each time an AppImage runs, its runtime directory is different, so that means that the default file paths (InfoSoundName & friends) stored in $HOME/.config/PCSX2/inis/PCSX2.ini point to an invalid location that will change after another AppImage execution. BTW, this is presumably happening too in portable versions for Windows (normal .zip after creating the portable.ini file so that config is saved inside the program dir).

Proposed solution: Leave the parameters unset in the .ini unless the user picks specific wav files in the system. But regenerate the default paths in memory when PCSX2 starts, so that a stale path (to an AppImage mount that might not exist anymore) isn't saved.

Have a nice day

Reproduction Steps

Use PCSX2 AppImage and look at the .wav file paths on the achievements interface or find them in the PCSX2.ini config file.

Expected Behavior

Handle the default paths as relative paths from the runtime directory

PCSX2 Revision

v2.6.3

Operating System

Linux (64bit) - Specify distro below

If Linux - Specify Distro

Debian

Logs & Dumps

No response

[Mrlinkwii]

i could be wrong , but i believe this is working as intended because by default it uses the message.wav etc which are found in the resources folder and then allows the user to change it they wish

[llsant]

But the default may point to a wrong location. Concrete steps to reproduce (just tried): Use the AppImage version on Linux. Go to settings, enable achievements, set to the default value. Then close everything. Open the AppImage again. Now the paths are pointing to files that don't exist (the previous AppImage mount point).

[kamfretoz]

Should be fixed already by #14269, can you update to the latest nightly and confirm? @llsant

[llsant]

I used the latest nightly on the web, file name "pcsx2-v2.7.521-linux-appimage-x64-Qt.AppImage". I'm not sure if that includes the #14269 patch because it's on the same day and I can't see the time of the day in the releases page. In any case, the answer is no. The issue still happens in PCSX2's web "latest nightly" "pcsx2-v2.7.521-linux-appimage-x64-Qt.AppImage", the old path is saved even in ephemeral AppImages. Not sure whether the patch is actually included.

[kamfretoz]

In any case, the answer is no. The issue still happens in PCSX2's web "latest nightly" "pcsx2-v2.7.521-linux-appimage-x64-Qt.AppImage", the old path is saved even in ephemeral AppImages. Not sure whether the patch is actually included.

Have you ACTUALLY tested it? Try downloading the absolute latest nightly and make sure, because i just tested it and it works fine.

2026-08-17.00-52-08.mp4

[llsant]

I was indeed in the latest nightly, I double checked everything, problem solved. I was testing it in a different way than you (you launched a clean slate PCSX2). Basically in the new version the "reset path" button now unsets the entries in the .ini file instead of hardcoding the current defaults, which is pretty nice. However, due to autosaving, the mere fact of clicking the text input field (and not changing anything) does indeed save the path in the .ini.

Suggestion: Maybe the best option to avoid accidental misconfigurations by AppImage users is to just replicate the .ini in the interface. If the path is unset, just show it as empty/unset in the interface, and if the user edits the text field but sets it empty, literally save that in the .ini and interpret it as the default path.

Have a nice day!

[kamfretoz]

However, due to autosaving, the mere fact of clicking the text input field (and not changing anything) does indeed save the path in the .ini.

ah yea, i see what you mean. ill take care of it after 2.8