[GH-ISSUE #91] Unable to launch AppImage on CachyOS #51

Open
opened 2026-02-17 17:11:56 -05:00 by yindo · 5 comments
Owner

Originally created by @tomorrow-nf on GitHub (Aug 1, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/91

Attempting to run the Drop.Desktop.Client_0.3.1_amd64.AppImage client on CachyOS but hitting the following error:

Could not create GBM EGL display: EGL_SUCCESS. Aborting...
fish: Job 1, './Drop.Desktop.Client_0.3.1_amd…' terminated by signal SIGABRT (Abort)

Client seems to start up and immediately crash.

  • Open NVidia drivers 575.64.05
  • Linux 6.16.0-5-cachyos
  • KDE Plasma 6.4.3
Originally created by @tomorrow-nf on GitHub (Aug 1, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/91 Attempting to run the Drop.Desktop.Client_0.3.1_amd64.AppImage client on CachyOS but hitting the following error: > Could not create GBM EGL display: EGL_SUCCESS. Aborting... > fish: Job 1, './Drop.Desktop.Client_0.3.1_amd…' terminated by signal SIGABRT (Abort) Client seems to start up and immediately crash. * Open NVidia drivers 575.64.05 * Linux 6.16.0-5-cachyos * KDE Plasma 6.4.3
yindo added the confirmedduplicatebug labels 2026-02-17 17:11:56 -05:00
Author
Owner

@DecDuck commented on GitHub (Aug 1, 2025):

Can you try the workaround mentioned here for NVIDIA?

https://docs.droposs.org/docs/guides/client-troubleshooting

@DecDuck commented on GitHub (Aug 1, 2025): Can you try the workaround mentioned here for NVIDIA? https://docs.droposs.org/docs/guides/client-troubleshooting
Author
Owner

@tomorrow-nf commented on GitHub (Aug 1, 2025):

Can you try the workaround mentioned here for NVIDIA?

https://docs.droposs.org/docs/guides/client-troubleshooting

I should've mentioned, apologies: I did see these steps but it doesn't seem that the .desktop file even gets created before the AppImage fails out.

@tomorrow-nf commented on GitHub (Aug 1, 2025): > Can you try the workaround mentioned here for NVIDIA? > > https://docs.droposs.org/docs/guides/client-troubleshooting I should've mentioned, apologies: I did see these steps but it doesn't seem that the .desktop file even gets created before the AppImage fails out.
Author
Owner

@DecDuck commented on GitHub (Aug 1, 2025):

Oh sorry, AppImages don't use .desktop files.

You can run the workaround via the command line like this:
WEBKIT_DISABLE_DMABUF_RENDERER=1 ./<appimagename>.appimage

@DecDuck commented on GitHub (Aug 1, 2025): Oh sorry, AppImages don't use .desktop files. You can run the workaround via the command line like this: `WEBKIT_DISABLE_DMABUF_RENDERER=1 ./<appimagename>.appimage`
Author
Owner

@tomorrow-nf commented on GitHub (Aug 1, 2025):

Ah gotcha, I may be stupid

Seems like it made some progress, immediately followed by this new one:

panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libappindicator-sys-0.9.0/src/lib.rs:41:5:
Failed to load ayatana-appindicator3 or appindicator3 dynamic library
/usr/lib/libayatana-ido3-0.4.so.0: undefined symbol: g_once_init_leave_pointer
/usr/lib/libappindicator3.so.1: undefined symbol: g_once_init_leave_pointer
/usr/lib/libayatana-ido3-0.4.so.0: undefined symbol: g_once_init_leave_pointer
/usr/lib/libappindicator3.so: undefined symbol: g_once_init_leave_pointer
fish: Job 1, 'WEBKIT_DISABLE_DMABUF_RENDERER=…' terminated by signal SIGABRT (Abort)

Double checked and I do have libayatana-appindicator and libappindicator-gtk3 installed. I'm actually seeing this exact same error on my steam deck, but didn't want to flood the reports 😅

@tomorrow-nf commented on GitHub (Aug 1, 2025): Ah gotcha, I may be stupid Seems like it made some progress, immediately followed by this new one: > panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libappindicator-sys-0.9.0/src/lib.rs:41:5: > Failed to load ayatana-appindicator3 or appindicator3 dynamic library > /usr/lib/libayatana-ido3-0.4.so.0: undefined symbol: g_once_init_leave_pointer > /usr/lib/libappindicator3.so.1: undefined symbol: g_once_init_leave_pointer > /usr/lib/libayatana-ido3-0.4.so.0: undefined symbol: g_once_init_leave_pointer > /usr/lib/libappindicator3.so: undefined symbol: g_once_init_leave_pointer > fish: Job 1, 'WEBKIT_DISABLE_DMABUF_RENDERER=…' terminated by signal SIGABRT (Abort) Double checked and I do have libayatana-appindicator and libappindicator-gtk3 installed. I'm actually seeing this exact same error on my steam deck, but didn't want to flood the reports 😅
Author
Owner

@DecDuck commented on GitHub (Aug 1, 2025):

I think the AppImage is broken for non-Debian based distros, due to that dependency.

From my understanding, CachyOS is based on Arch Linux. We have AUR packages that should work, if you want to try those while I fix the AppImage:

https://aur.archlinux.org/packages?O=0&K=drop-oss-app

@DecDuck commented on GitHub (Aug 1, 2025): I think the AppImage is broken for non-Debian based distros, due to that dependency. From my understanding, CachyOS is based on Arch Linux. We have AUR packages that should work, if you want to try those while I fix the AppImage: https://aur.archlinux.org/packages?O=0&K=drop-oss-app
yindo changed title from Unable to launch AppImage on CachyOS to [GH-ISSUE #91] Unable to launch AppImage on CachyOS 2026-06-05 14:24:31 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop-app#51