Appimages stopped working

[medmedin2014]

Describe the bug

All my downloaded Appimage files stopped working and finish with: zsh: segmentation fault (core dumped)

Expected behavior

Appimages should open like they did before.

Steps to reproduce the issue

No response

Screenshots

No response

Distribution and desktop environment

Operating System: Manjaro Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.7-1-MANJARO (64-bit) Graphics Platform: Wayland

Installed AppImageLauncher version

AppImageLauncher version 2.2.0 (git commit 0f91801), built on 2022-05-29 15:58:36 UTC

List of AppImages you tried

No response

Additional context

No response

[ximi75]

I have the same problem

Betriebssystem: Manjaro Linux KDE-Plasma-Version: 5.27.6 KDE-Frameworks-Version: 5.108.0 Qt-Version: 5.15.10 Kernel-Version: 6.4.7-1-MANJARO (64-bit) Grafik-Plattform: X11

[Saashiguma]

I started experiencing the exact same thing yesterday on my Arch Linux machine shortly after an update. I've tried the following things to troubleshoot to no avail so far:

• Reinstalling AppImageLauncher from AUR
• Trying to install AppImageLauncher-git from AUR (it fails with exit status 4)
• Launching appimages directly from terminal with ./appname.AppImage
• Updating appimages with latest versions
• chmod +x on appimage files all over again
• Switching sessions from Awesome WM to XFCE and GNOME

I suspect the update is the culprit, but I'm not even sure where to start troubleshooting considering all I ever see when attempting to run an AppImage right now is this:

(AppImageLauncher:1731): Gtk-WARNING **: 11:38:53.697: Theme parsing error: gtk.css:3932:55: Using one color stop with linear-gradient() is deprecated. zsh: segmentation fault (core dumped) ./beeper-3.66.23_0d2b49309ff3a60a6fc28de0edde5d44.AppImage

If I could at least figure out what updated package broke this, then I would know what to try and rollback to see if I'm onto something, but it was a big update and I'm not sure where to start. I'll update if I get it working again.

[efgeorge]

This happened to me too since yesterday after an update on Arch Linux. I tried almost everything that @Saashiguma tried, alongise with:

• downgrading boost (I don't know why I thought it could be something related to it)
• checking my pacman logs to see if there was any direct upgrade to one of appimagelauncher's dependencies, but found nothing
• re-downloading the appimage I want to execute, including and older version of it

None of these worked so far.

[yochananmarqos]

This has nothing to do with AppImageLauncher. It's only a frontend to manage AppImages.

It's an issue with squashfuse 0.3.0, see https://github.com/vasi/squashfuse/issues/105

[Saashiguma]

This has nothing to do with AppImageLauncher. It's only a frontend to manage AppImages.

It's an issue with squashfuse 0.3.0, see vasi/squashfuse#105

Thank you so much for the lead here. I incorrectly assumed it did have to do with AppImageLauncher because my terminal segfault still referenced AppImageLauncher:1731 when the apps failed to launch.

However, I followed your link and tried the downgrade workaround suggested by user DianaNites. Now my AppImages actually work again!

[TheAssassin]

I have no idea how some system-provided squashfuse would break AppImageLauncher, but I'm glad that downgrade fixes your problem.