Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AppImage Crash (Arch+Gnome Reproduced) #18

Closed
psadi opened this issue Jan 27, 2025 · 8 comments
Closed

AppImage Crash (Arch+Gnome Reproduced) #18

psadi opened this issue Jan 27, 2025 · 8 comments
Assignees
Labels
duplicate This issue or pull request already exists wontfix This will not be worked on

Comments

@psadi
Copy link
Owner

psadi commented Jan 27, 2025

In continuation of the reported issue #12 The fix Provided in PR #13 didn't work as intended. App-image crashed with exit code 139 and the fallback logic didn't get executed (Mostly the application started and the rendering issue raised within the app hence it can't be caught runtime)

Image

The only workaround at the moment is to execute the application with manual fallback either by running GDK_BACKEND=x11 ghostty or adding it to .bashrc / .zshrc

@psadi psadi added bug Something isn't working duplicate This issue or pull request already exists labels Jan 27, 2025
@psadi psadi self-assigned this Jan 27, 2025
@CM-IV
Copy link

CM-IV commented Feb 2, 2025

Same issue occurs under Aurora OS (Fedora Silverblue) w/ KDE

Image

@Samueru-sama
Copy link
Contributor

The only workaround at the moment is to execute the application with manual fallback either by running GDK_BACKEND=x11 ghostty or adding it to .bashrc / .zshrc

Or just force GDK_BACKEND=x11 in the AppRun always.

@psadi
Copy link
Owner Author

psadi commented Feb 3, 2025

Or just force GDK_BACKEND=x11 in the AppRun always.

I'm leaning towards keeping things as native as possible (We could add a note in the troubleshooting section as an interim solution) as I'm unaware on the side-effects or if we miss out on any-other features by forcing x11 on Wayland systems.

@Samueru-sama
Copy link
Contributor

Samueru-sama commented Feb 3, 2025

or if we miss out on any-other features by forcing x11 on Wayland systems.

Does that mean that the appimage actually works on some wayland systems and it isn't using xwayland or similar?

If it always fails to work in wayland then adding GDK_BACKEND=x11 for now is the only solution.

@psadi
Copy link
Owner Author

psadi commented Feb 3, 2025

Does that mean that the appimage actually works on some wayland systems and it isn't using xwayland or similar?

Probably yes, I can confirm from the few testing i did that this issue occurs only on Gnome based DE's. I had no issues running the AI on U24.04 (Gnome wayland) and Manjaro (KDE wayland) and i soon intend to test the same in Arch (XFCE + Wayland)

@Samueru-sama
Copy link
Contributor

Probably yes, I can confirm from the few testing i did that this issue occurs only on Gnome based DE's. I had no issues running the AI on U24.04 (Gnome wayland) and Manjaro (KDE wayland) and i soon intend to test the same in Arch (XFCE + Wayland)

case "${XDG_CURRENT_DESKTOP}" in
    *GNOME*|*gnome*)
        export GDK_BACKEND=x11
        ;;
esac

And more checks could be added to narrow when to set the variable.

It is likely that bundling opengl will also fix the issue since we had a similar issue with webkit2gtk, the lib needs a specific version of opengl to work otherwise you get a blank screen. However that means a significant increase in the appimage size.

I've recently been experimenting with reducing the size of llvm, since that's a huge library that opengl mesa links to, and it helps 1 2 but I don't have arm versions of this library, not to mention I make it on Artix linux which doesn't even have arm support iirc.

@psadi
Copy link
Owner Author

psadi commented Feb 3, 2025

case "${XDG_CURRENT_DESKTOP}" in
    *GNOME*|*gnome*)
        export GDK_BACKEND=x11
        ;;
esac

And more checks could be added to narrow when to set the variable.

We could add these checks if the error were to occur in all gnome based distro's. To keep things simple i think its probably better to let the users handle the fallback logic when faced (until we find a fix to pin down the rc)

It is likely that bundling opengl will also fix the issue since we had a similar issue with webkit2gtk, the lib needs a specific version of opengl to work otherwise you get a blank screen. However that means a significant increase in the appimage size.

Yeah, we could do that, but lets avoid atm to keep the AI size as minimal as possible (as this is not frequently occurring)

@psadi psadi added invalid This doesn't seem right wontfix This will not be worked on and removed invalid This doesn't seem right bug Something isn't working labels Feb 4, 2025
@psadi
Copy link
Owner Author

psadi commented Feb 4, 2025

Closing this issue with a manual workaround to fallback to X11 GDK_BACKEND

@psadi psadi closed this as completed Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants