AppFlowy [Bug] No GL implementation is available with AppImage on Arch Linux/EndeavourOS with Wayland

Bug Description

Can not launch app through AppImage on Arch Linux/EndeavourOS with Wayland.

Operating System: EndeavourOS KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.10-arch1-1 (64-bit) Graphics Platform: Wayland

How to Reproduce

Download AppImage from website, and then fix it by utilizing https://github.com/AppFlowy-IO/AppFlowy/issues/3836#issuecomment-1855700903 or https://github.com/AppFlowy-IO/AppFlowy/issues/3836#issuecomment-2294867618

$ LANG=C ./AppFlowy-x86_64.AppImage 

(AppFlowy:13790): Gtk-WARNING **: 22:20:45.035: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.

(AppFlowy:13790): Gdk-CRITICAL **: 22:20:45.063: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed

** (AppFlowy:13790): WARNING **: 22:20:45.063: Failed to initialize GLArea: No GL implementation is available

** (AppFlowy:13790): WARNING **: 22:20:45.064: gtk.dart: failed to call method: No engine to send to

** (AppFlowy:13790): WARNING **: 22:20:45.064: gtk.dart: failed to call method: No engine to send to

** (AppFlowy:13790): WARNING **: 22:20:45.064: gtk.dart: failed to call method: No engine to send to

** (AppFlowy:13790): WARNING **: 22:20:45.064: gtk.dart: failed to call method: No engine to send to

** (AppFlowy:13790): WARNING **: 22:20:45.064: gtk.dart: failed to call method: No engine to send to

** (AppFlowy:13790): WARNING **: 22:20:45.064: gtk.dart: failed to call method: No engine to send to

** (AppFlowy:13790): CRITICAL **: 22:20:45.090: void fl_keyboard_manager_sync_modifier_if_needed(FlKeyboardManager *, guint, double): assertion 'FL_IS_KEYBOARD_MANAGER(self)' failed

Expected Behavior

App launched without problem.

Operating System

Arch Linux/EndeavourOS

AppFlowy Version(s)

0.6.7.1

Screenshots

Additional Context

This error only happened in Wayland. Switching the GTK backend to X11 can avoid this issue. The workaround is to set GDK_BACKEND=x11 when launching the AppImage.