Some AppImage app not being executed

[shawe]

Pre-submit checks

• I checked for similar issues beforehand, but could not find any, not even closed ones. I could not add my bug report to any existing issue.
• I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.

Describe the bug

Some apps are not being executed, and when try it from shell I only can see that:

$ ./PrusaSlicer-2.8.0+linux-x64-GTK3-202406271021-Ubuntu-24-04_8faf233db5caf189ea8dd8b57f269866.AppImage 
AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1)
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)
execv error: No such file or directory

Some other apps, works without problems:

$ ./Bitwarden-2024.6.3-x86_64_e9141edc42f532ea9d00c3b7ea7a524a.AppImage 
AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1)
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)
00:30:16.457 › State version: 65
00:30:16.459 › Migrator MinVersionMigrator (to version 3) should migrate: false - up
00:30:16.460 › Migrator RemoveEverBeenUnlockedMigrator (to version 4) should migrate: false - up
00:30:16.460 › Migrator AddKeyTypeToOrgKeysMigrator (to version 5) should migrate: false - up
00:30:16.460 › Migrator RemoveLegacyEtmKeyMigrator (to version 6) should migrate: false - up
00:30:16.460 › Migrator MoveBiometricAutoPromptToAccount (to version 7) should migrate: false - up
00:30:16.460 › Migrator MoveStateVersionMigrator (to version 8) should migrate: false - up
00:30:16.460 › Migrator MoveBrowserSettingsToGlobal (to version 9) should migrate: false - up
00:30:16.460 › Migrator EverHadUserKeyMigrator (to version 10) should migrate: false - up
00:30:16.460 › Migrator OrganizationKeyMigrator (to version 11) should migrate: false - up
00:30:16.460 › Migrator MoveEnvironmentStateToProviders (to version 12) should migrate: false - up
00:30:16.460 › Migrator ProviderKeyMigrator (to version 13) should migrate: false - up
00:30:16.460 › Migrator MoveBiometricClientKeyHalfToStateProviders (to version 14) should migrate: false - up
00:30:16.460 › Migrator FolderMigrator (to version 15) should migrate: false - up
00:30:16.460 › Migrator LastSyncMigrator (to version 16) should migrate: false - up
...

Expected behavior

The expected behavior was to be opened normally how other apps, with double click or from shell.

There are no blocked process of any other instance of PrusaSlicer locked.

Steps to reproduce the issue

I only need to try to run the app and not running.

This seems to not be reproducible to you, and for this reason you say me that I must open a new issue.

It's possible that the problem was caused for some system differences, but I don't know why exactly share here. A list of repositories and a list of installed packages?

I know that this non-details issue are not useful to help with this problem. Please, ask me what you need to be provided to help to found the problem.

Screenshots

Distribution and desktop environment

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
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=noble
LOGO=ubuntu-logo

$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04 LTS"
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
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=noble
LOGO=ubuntu-logo

$ kinfocenter
Kubuntu 24.04 LTS
KDE Plasma: 5.27.11
KDE Frameworks: 5.115.0
Qt: 5.15.13
Kernel: 6.8.0-40-generic (64 bits)
X11

$ plasmashell --version
plasmashell 5.27.11

$ kf5-config --version
Qt: 5.15.13
KDE Frameworks: 5.115.0
kf5-config: 1.0

Installed AppImageLauncher version

AppImageLauncher version 2.2.0 (git commit 0f91801), built on 2022-11-02 23:51:55 UTC

List of AppImages you tried

Working

• Bitwarden-2024.7.1-x86_64_3c0d21cb616089f838275bb941b2ab65.AppImage
• upscayl-2.11.5-linux_f887236cb60bbdbab2c1dd7e35f1fefd.AppImage
• Rambox-2.3.4-linux-x64_4a34b75d403096170fac6a048bd017f1.AppImage
• JetBrains Toolbox 2.4.1.32573, ubuntu 24.04 (Linux 6.8.0-40-generic), x64

Not working

• PrusaSlicer-2.8.0+linux-x64-GTK3-202406270929_dfd3cdac76b94d77e7d6b2eac3000f92.AppImage
• PrusaSlicer-2.8.0+linux-x64-GTK3-202406271021-Ubuntu-24-04_8faf233db5caf189ea8dd8b57f269866.AppImage

Additional context

Some days ago (7/7/2024 when download it), upscayl also was not opening. I maintain it because I won't lose this app to test it, and now I can try it apparently without problems.

I copied the config files from /home/francesc/.config/PrusaSlicer/ to /home/francesc/.var/app/com.prusa3d.PrusaSlicer/config/PrusaSlicer/ and the flatpak version of PrusaSlicer is working as before with with AppImage version. Then config files seems to be good.

[Kiendeleo]

I am also having issues with Prusaclicer. The 2.8 version will not work with AppImage Launcher

[shawe]

I am also having issues with Prusaclicer. The 2.8 version will not work with AppImage Launcher

Thanks for confirm that I’m not the only one who has this strange problem.

Anythink I can do to help with more accurate information let me know. I’m also can share with you remote access if you think can help you more.

[iTrooz]

I think that this is relevant: zen-browser/desktop#312 (comment)

[mhkdepauw]

Bump for zen-browser/desktop#312 (comment) , I'm having the same issue with the zen appimage.

[TheAssassin]

Cannot reproduce in a quick 5-minute evaluation. Needs more investigation.

[shawe]

Cannot reproduce in a quick 5-minute evaluation. Needs more investigation.

You are welcome to try it from my PC and try to gather relevant information that may help you.

Currently the bug I reported still has the same problem.