Add wayland plugin to the appimage

[Twig6943]

 /home/twig/Downloads/Xplist-Linux-x86_64.appimage 
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.

Aborted                    (core dumped) /home/twig/Downloads/Xplist-Linux-x86_64.appimage

Related commit: hasherezade/pe-bear@ae49906

[ic005k]

Fix Qt platform plugin "wayland" missing error (Qt5 AppImage)

This error occurs because the Qt5 program cannot load the Wayland display plugin on your Linux system. There are two solutions available.

Solution 1: Install Qt5 Wayland dependency (Permanent fix for Wayland desktop)

If your system uses Wayland display server (default for modern Ubuntu/Debian), install the missing Qt5 Wayland library:

sudo apt update
sudo apt install qtwayland5

After installation, double-click the AppImage directly to launch normally without extra commands.

Solution 2: Force use XCB/X11 platform (Temporary universal workaround)

Works for both Wayland and X11 desktops, no extra packages required. Run the AppImage with environment variable in terminal:

QT_QPA_PLATFORM=xcb /home/twig/Downloads/Xplist-Linux-x86_64.appimage

Notes

1. If your desktop environment uses Xorg (X11), installing qtwayland5 will not resolve the issue, you must use Solution 2.
2. Solution 2 is recommended for quick testing without sudo permissions.

[Twig6943]

This should be included in the appimage. xcb is included in the appimage. as of right now I am using xwayland to run the app, but yea it should be added in like the commit I linked above

I already have qt5-wayland & qt6-wayland installed. This needs to be added into the appimage

[ic005k]

Risks of Bundling qt5-wayland & qt6-wayland into AppImage + Cross-Linux Compatibility Analysis

1. Major Potential Risks

1.1 ABI incompatibility between bundled Wayland plugins and system Wayland libraries (Critical issue)

Qt Wayland platform plugins link tightly against system-level Wayland components (libwayland-client, protocol extensions, compositor interfaces like KWin/Mutter/Sway).

• Your bundled Wayland plugins are compiled against a fixed version of Wayland libraries on your build machine.
• If end-user’s system Wayland libraries are newer or older, missing symbols, broken struct layouts or protocol mismatches will occur.
• Common failures: Black window, rendering crash, error could not load Qt platform plugin "wayland".
• Contrast: XCB/X11 maintains stable ABI for decades with far fewer compatibility breaks.

1.2 Graphics driver & rendering pipeline conflicts

• Bundled Wayland plugins ship their own QSG OpenGL/Vulkan render backends, which may mismatch user’s Mesa/NVIDIA graphics drivers.
• Consequences: Screen tearing, graphical glitches, failed GPU context creation.
• NVIDIA proprietary drivers already have poor native Qt Wayland support; bundled plugins amplify these stability issues.

1.3 Larger AppImage file size

qt5-wayland and qt6-wayland include platform plugins, Wayland protocol extensions, EGL rendering modules and cursor components. Shipping both Qt5 and Qt6 sets will drastically inflate the single AppImage binary, slowing down distribution and runtime extraction.

1.4 Qt5 / Qt6 library load collisions

Since your AppImage carries both Qt major versions, dynamic linkers may accidentally load mismatched QtCore/QtGui libraries when searching Wayland plugin paths. Misloaded platform plugins lead to instant startup crashes.

1.5 Missing distro-specific patches

Official upstream Qt Wayland code lacks custom patches maintained by each Linux distro:

• High-DPI scaling fixes
• Input method (IME) integration
• Window management rules for desktop environments
• Touchscreen/tablet adjustments
  Users on different distros will face broken scaling, unresponsive input methods or misplaced popups.

1.6 Broken XWayland fallback

If your bundled Wayland plugin fails to initialize, Qt should automatically fall back to XCB via XWayland. Poor packaging may force Qt to prioritize the faulty Wayland plugin first, exiting immediately without trying the X11 compatibility layer.

2. Will this work on all Linux distributions?

No full cross-Linux compatibility is guaranteed. Bundling Wayland plugins improves native Wayland startup chances but still fails on many environments.

Environments that usually work

1. Distros with Wayland library versions matching your build base (e.g. same Ubuntu LTS generation, matching Fedora major release)
2. Systems using open-source Mesa drivers (Intel/AMD GPUs)
3. Lightweight Wayland compositors (Sway, Weston)

Environments prone to failures

1. Legacy old distros (Ubuntu 20.04 or earlier): Outdated system libwayland missing symbols required by new bundled plugins
2. Rolling-release distros (Arch, Gentoo): Constantly updated Wayland stacks break statically bundled plugin ABI
3. Systems with NVIDIA proprietary graphics drivers
4. Immutable Linux distros (NixOS, Fedora Silverblue): Specialized library paths, sandbox restrictions and permission limits
5. Pure X11 desktops without any Wayland stack: Wayland plugins remain unused (no crash risk, just wasted bundle size)

3. Mitigation recommendations to reduce risks

1. Keep XCB bundled as the reliable fallback platform plugin
2. Build your AppImage on an older LTS base system (e.g. Ubuntu 22.04) — older build-time Wayland dependencies provide wider downward ABI compatibility
3. Strictly separate Qt5 and Qt6 plugin directories via QT_PLUGIN_PATH in your AppRun script to eliminate cross-version load conflicts
4. Add fault-tolerant startup logic to prioritize Wayland then fall back to XCB automatically

   export QT_QPA_PLATFORM=wayland
   ./YourApp 2>/dev/null || {
       export QT_QPA_PLATFORM=xcb
       ./YourApp
   }

5. Detect active Wayland sessions in the startup script; skip Wayland plugin logic entirely if only an X11 session exists

Summary

1. Core risk: Wayland libraries do not offer long-term stable ABI unlike XCB, resulting in crashes, rendering defects, larger binary size and Qt version collisions.
2. Compatibility limit: Cannot support every Linux distro seamlessly; stable performance is limited to matching-generation distros with open GPU drivers.
3. Main benefit: End users no longer need manual installation of system qt*-wayland packages to run the app natively under Wayland, bypassing the slower XWayland compatibility layer with better high-DPI and touch input behavior.

[Twig6943]

I really don't want to be rude or start anything but please stop with the ai responses. There's nothing wrong about bundling qt wayland plugin (all mainstream emulator software do for example)

Again I'm sorry if this sounds rude but what the ai says is straight up bs

[Ferynix]

I really don't want to be rude or start anything but please stop with the ai responses. There's nothing wrong about bundling qt wayland plugin (all mainstream emulator software do for example)

Again I'm sorry if this sounds rude but what the ai says is straight up bs

Not rude at all.. the amount of this shit present in basically every github repo now is actually painful. It just makes development and troubleshooting that much more irritating.