Crash on sleep

[Samueru-sama]

We had an issue about crash on sleep that gets fixed when either the appimage is extracted or an alternative runtime is used.

I already had the suspicion because of this other issue I saw at linuxdeploy.

So at this point I'm fairly certain that there is a bug with the runtime causing this.

[probonopd]

After looking at pkgforge-dev/ghostty-appimage#27 (comment), it would be interesting to see what happens if the user

1. Mounts the AppImage using ./Ghostty-1.1.0-x86_64.AppImage --appimage-mount
2. Goes to sleep
3. Wakes from sleep
4. Tries to access the files at the mountpoint - are the files still mounted? Are there errors when opening/reading them? Or is there only an error when trying to run AppRun?

On which operating systems and sleep modes can this be reproduced?

[Samueru-sama]

@romainreignier Can you try the above with the AppImage that crashes on sleep?

[romainreignier]

Hi @probonopd
I have tried your procedure and once resumed, the temp directory is not there anymore.

./Ghostty-1.1.2-x86_64.AppImage --appimage-mount
/tmp/.mount_GhosttJdaLMk

ls /tmp/.mount_GhosttJdaLMk
"/tmp/.mount_GhosttJdaLMk": No such file or directory (os error 2)

This is on Kubuntu 22.04.5:

cat /etc/os-release 
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

About the sleep mode, I am not sure. I can tell that if I click on Sleep in KDE and resume a few seconds later, there is no issue.
But I have a crash every morning with the computer sleeping since the previous end of day.

See the suspend and resume systemd logs in case you can find anything useful about the sleep mode.

resume_logs.txt

[probonopd]

Thanks @romainreignier. It seems like your AppImage is not using https://github.com/AppImage/type2-runtime but https://github.com/VHSgunzo/uruntime. So closing here, please report at https://github.com/VHSgunzo/uruntime/issues.
Thanks!

Reference:

• --appimage-version should mention uruntime VHSgunzo/uruntime#6

[probonopd]

If you can reproduce the issue using the AppImages from https://github.com/AppImage/appimagetool/releases/tag/continuous, then type2-runtime is also affected and we can reopen this.

[Samueru-sama]

No @probonopd the issue is happening with the type2-runtime and we fixed it by switching to the uruntime, the appimage with the uruntime no longer crashes on sleep.

WIth that said I don't know why @romainreignier tested here with version 1.1.2 which there are 3 separate releases and only the oldest one of that one is using the type2-runtime.

Here we were told that there was no crash anymore on sleep, that artifact is using the uruntime.

I later asked @romainreignier to test the AppImage that crashes on sleep, which is v1.1.2+1 and uses the type2-runtime and there was no crash anymore. when extracted but it crashes when run normally.

TLDR:

• v1.1.2+1 and older crash on sleep unless extracted, these use type2-runtime.

• v1.1.2+2 and newer do not crash on sleep under any condition, these use uruntime.

[Samueru-sama]

On top of that I had already seen this issue at linuxdeploy which happened after it was switched to use the static type2-runtime, and in that case the dev says that the crash does not happen when extracted as well.

[probonopd]

Sorry, my bad. Was tired from dayjob work ;)

[probonopd]

Can you reproduce the issue using the AppImages from https://github.com/AppImage/appimagetool/releases/tag/continuous though?

[Samueru-sama]

Can you reproduce the issue using the AppImages from https://github.com/AppImage/appimagetool/releases/tag/continuous though?

Me? I can't but that's likely because I have one of those chinese X99 motherboards that don't have the ultra slow power states enabled, when I send the PC to sleep it doesn't really go to sleep lol.

I tried in any case, here is what I was going to test:

You can find out if an appimage is using the uruntime by grepping the URUNTIME_MOUNT string which is an internal env variable of it which is not present in the type2-runtime.

Also notice that the mount point names are different, while the type2-runtime it is .mount_ghosttHlAdkm in the uruntime it is a bunch of numbers .mount_5354263854163925111.

So @romainreignier was indeed testing the right appimage here because --appimage-mount had the .mount_Ghostt*** output.

[romainreignier]

Hi @probonopd indeed, I was testing with the version v1.1.2+1 using type2-untime.
If you need it, how should I use appimagetool-x86_64.AppImage to keep it running while the PC goes to sleep?

[probonopd]

As above,

1. appimagetool-x86_64.AppImage --appimage-mount
2. Go to sleep
3. Wake from sleep
4. Try to access the files at the mountpoint - are the files still mounted? Are there errors when opening/reading them? Or is there only an error when trying to run AppRun?

[romainreignier]

I can confirm the same behavior.

./appimagetool-x86_64.AppImage --appimage-mount
/tmp/.mount_appimabGPOao

After the sleep:

 ls /tmp/.mount_appimabGPOao
"/tmp/.mount_appimabGPOao": No such file or directory (os error 2)