saturneric
AppImage: no wayland libraries. unable to work on wayland natively
When xwayland is disabled the app fails to work because it cannot do wayland natively. QT6 supports wayland. This AppImage does not appear to contain Wayland libraries in it.
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.
You may try the nightly build and see if it works. If it does, the reason will be that I forgot to add the wayland plugin in the release version of AppImage. :(
Some progress.
qt.qpa.wayland: No shell integration named "xdg-shell" found qt.qpa.wayland: No shell integration named "wl-shell" found qt.qpa.wayland: No shell integration named "ivi-shell" found qt.qpa.wayland: No shell integration named "qt-shell" found qt.qpa.wayland: Loading shell integration failed. qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell") qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. qt.qpa.xcb: could not connect to display qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland, wayland-egl, minimal, linuxfb, offscreen, xcb, eglfs, vkkhrdisplay, minimalegl, vnc.
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
I just added these dependencies. You can try it again with the latest nightly build.
No change? Also I think xcb is not wayland.
qt.qpa.wayland: No shell integration named "xdg-shell" found
qt.qpa.wayland: No shell integration named "wl-shell" found
qt.qpa.wayland: No shell integration named "ivi-shell" found
qt.qpa.wayland: No shell integration named "qt-shell" found
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland, wayland-egl, minimal, linuxfb, offscreen, xcb, eglfs, vkkhrdisplay, minimalegl, vnc.
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Are you using fedora which uses only wayland now?
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Are you using fedora which uses only wayland now?
Sway with xwayland disabled.
Be it x11 or xwayalnd every single app will be able to spy on all other apps which is not suitable for GPG software. Native wayland is preferred. Else you need to use Xephyr and the like to sandbox x11 apps (which happens to also disable clipboard functionality).
I was able to "fix" GpgFrontend by doing --extract-appimage to it and another appimage that works on wayland natively and then copying and overwriting one to the other. So this is a configuration problem on your end.
Okay. I understand and will take care if this issue. But I may need some time, since I'm contribute to this project on my free time. Once I resolve this, I will send the update informaition here.
Be it x11 or xwayalnd every single app will be able to spy on all other apps which is not suitable for GPG software. Native wayland is preferred. Else you need to use Xephyr and the like to sandbox x11 apps (which happens to also disable clipboard functionality).
Resonable. I didn't known that before. I'll also do a research on this point.
@handpickencounter Just fixed wayland support. I tested it with wayland on Ubuntu-24.04. It worked. You can try the latest nightly version and verify.
@handpickencounter Just fixed wayland support. I tested it with wayland on Ubuntu-24.04. It worked. You can try the latest nightly version and verify.
I don't think it was running on wayland for you.
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
As I said before it works when I just copy another appimage's contents (that has wayland working) overriding yours. So it should be a simple misconfiguration problem, but I know nothing about appimage other than --appimage-extract
After spending some time gathering information, I’ve hit a roadblock: I don’t have a suitable environment in which to reproduce and verify this issue. On one hand, the project relies on linuxdeployqt to generate the AppImage; however, as its README makes clear,
“linuxdeployqt does not contain any specific workarounds for Wayland which breaks many things. For best results, do not use Wayland.” 
On my end, I’m running Debian on a workstation with NVIDIA drivers, and due to compatibility constraints everything is being forced onto X11. I also tried spinning up a Fedora VM—Fedora being one of the leading Wayland-based distributions—but on the latest OS images KVM simply won’t start, likely because of my display configuration.
Accordingly, I’m going to put this issue on hold until one of the following occurs:
- An external breakthrough—either someone in the community figures out a workaround or the linuxdeployqt project adds proper Wayland support.
- I gain access to a stable Wayland environment, at which point I’ll pick up debugging and verifying the problem myself.
Realistically, this limitation may persist in v2.1.9 and possibly later releases unless the underlying Wayland support is addressed.
You could just build it with docker in an ubuntu environment (QT has excellent wayland support) and release the *.ubuntu.deb I usually extract a .deb and it always just works in my environment (glibc).
Currently, I do not provide official deb packages for GpgFrontend, mainly due to several reasons:
- GpgFrontend is not included in the official Debian or Ubuntu repositories, and maintaining a fully compliant deb package for all versions would be a significant effort.
- Different Debian/Ubuntu versions have different software environments. For example, the latest GpgFrontend requires gpgme 2.0, which is not available on many older LTS releases. This makes it difficult to support both current and legacy systems simultaneously.
- Supporting deb packages for older GpgFrontend versions running on legacy LTS systems would require providing long-term patch and bugfix support, which is not realistic for a mainly individually-maintained project.
Because of these reasons, the AppImage distribution is currently the most universal solution. As long as your system provides a basic desktop environment, you can run it without worrying about underlying dependencies or distribution compatibility.
That being said, the project does support building deb or rpm packages using CMake and CPack. If you are familiar with CMake, you can use cpack -G DEB to generate a deb package, or simply use make install for local installation. For special environments, it’s usually best to compile and install GpgFrontend directly in your own setup to ensure all dependencies are properly handled.
If you have better ideas or suggestions, feel free to discuss!
Additionally, GpgFrontend is now available as a Flatpak package (you can find it on Flathub). Flatpak usually offers better compatibility with Wayland and integrates well with most desktop environments. Have you tried the Flatpak version?