Appimage Disappears Upon Launch

[Saiyaken-PHOENIX]

Not sure if this is intended behavior, but I've managed to consistently replicate this on SteamOS. I prefer using appimages to the Flatpak versions due to portability and less dependency requirements.

Will test the appimage on Arch soon.

Observed Behavior:
Appimage vanishes after extracting and double-clicking/running the executable as is. Extracted/ran on Dolphin file viewer.

Expected Behavior:
Appimage does not disappear after launching

Operating System: SteamOS 3.7.10 Build: 20250618.2
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.11.11-valve19-1-neptune-611-g88b36d49a5e3 (64-bit)
Graphics Platform: X11
Partition: A
Processors: 8 × AMD Custom APU 0932
Memory: 11.5 GiB of RAM
Graphics Processor: AMD Custom GPU 0932
Manufacturer: Valve
Product Name: Galileo
System Version: 1

[sockenklaus]

I can confirm this behaviour on Fedora 42... It's really weird...

[ThienBienBlue]

This looks like a bug with the AppImage's AppRun file, in particular the following line

    echo AppImage, extract
    TMPDIR=$(mktemp -d)
    cp $ARGV0 "$TMPDIR/"
    cd $TMPDIR
    $ARGV0 --appimage-extract >/dev/null 2>&1
>>  rm $ARGV0  # This one!
    cd "squashfs-root/opt/eddie-ui/"

When I rebuild the AppImage with changes in the AppRun file to echo $TMPDIR; echo $ARGV0; pwd, I get

AppImage, extract
/tmp/tmp.2WrMBGz6nQ
/home/USER/path/to/Eddie_-_VPN_UI-x86_64.AppImage
/tmp/tmp.2WrMBGz6nQ
AppImage, run

indicating that the rm $ARGV0 call is removing the original AppImage instead of the copy inside the tmp directory. My best guess is that the script expects ARGV0=Eddie to always be a relative path.

Locally I updated that line to be the following and the AppImage stopped deleting itself.

rm "$TMPDIR/$(basename $ARGV0)"