Hi Terje, thank you for looking into the package. You are right: the AppImage carries only the X11 platform plugin of Qt, the Wayland plugins are not in it. There is a second half that your search could not show. The start script inside the AppImage (|AppRun|) sets |QT_QPA_PLATFORM=xcb| itself and so overrides what you set. Even with the plugins in the package you would still have ended up on XWayland. Both come from my build script, not from an accident in one build, and the new alpha AppImage of October 10 behaves the same. I will try to add Wayland as an opt-in: - The build script packs the Wayland plugins of Qt as well. - X11 stays the default, so nothing changes for anyone who just starts the AppImage. - If you set |QT_QPA_PLATFORM=wayland| before the start, the program uses Wayland. One honest warning: the port has only ever been tested on X11, and all my scripted tests run there. I expect rough edges under native Wayland, most likely with the floating panels, window positions and the keyboard handling of panels. That is why it will be opt-in and not the default for now. I will write here when an AppImage with the switch is online. If you then try it, reports about what breaks would help me a lot. The bug tracker at https://bug.cinelerra-gg.org has a category *Qt6 Alpha* for this. Your compositor and distribution in the report would be useful. Sam Am 09.10.26 um 22:56 schrieb Terje J. Hanssen via Cin:
Hi again,
Following up on my previous test above: Because forcing QT_QPA_PLATFORM=wayland still resulted in Cinelerra running under XWayland (xlsclients confirmed cin), I decided to have a look at the internal contents of the AppImage (CinGG-qt6-20261001-x86_64.AppImage).
After extracting the package (--appimage-extract), I ran a search for the Qt6 Wayland platform plugins (*wayland*.so). The search returned no matches, confirming that the Wayland QPA plugins are currently omitted from this build bundle.
Because these plugins are missing from the package, Qt6 has no choice but to fall back to XWayland, even if the environment variable is explicitly set.
Just wanted to share this finding in case it's helpful for possibly adjusting the build scripts/recipes for later releases!
Terje _______________________________________________ Cin mailing list --cin@lists.cinelerra-gg.org To unsubscribe send an email tocin-leave@lists.cinelerra-gg.org