Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.8
-
None
-
Linux/Wayland
Description
At some point the build fails because of two reasons:
- the buildsystem expects a display to run balsam
- even if the user has a display, the wayland QPA plugin hasn't been built yet and needs to be explicitly built using ninja qwayland-generic.
FAILED: qtquick3d/tests/baseline/scenegrabber/.ibl/OpenfootageNET_lowerAustria01-1024.ktx /home/builder/developer_build/qtquick3d/tests/baseline/scenegrabber/.ibl/OpenfootageNET_lowerAustria01-1024.ktx cd /home/builder/developer_build/qtquick3d/tests/baseline/scenegrabber && /home/builder/developer_build/qtbase/bin/balsam --no-plugins -o /home/builder/developer_build/qtquick3d/tests/baseline/scenegrabber/.ibl /home/builder/qt5-git/qtquick3d/tests/baseline/data/shared/maps/OpenfootageNET_lowerAustria01-1024.hdr qt.qpa.plugin: Could not find the Qt platform plugin "wayland,xcb" 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, linuxfb, eglfs, minimalegl, vkkhrdisplay, vnc, minimal, offscreen. Aborted
How to reproduce
- Create a new user without screen attached: useradd -m builder
- sudo su - builder
- mkdir build; cd build
- /path/to/qt5.git/configure -qpa wayland -developer-build -make examples ...
- ninja
P.S. a nice side-fix would be to mention after configure in config.summary that the "Wayland QPA plugin" is enabled. It's currently difficult to understand if the plugin is configured or not.
Attachments
Issue Links
- relates to
-
-
- Reported
-