Not able to run GUI for sample QT qml app

analage · May 7, 2025, 5:06pm

1: (3270) ->=library-loaded,id=“/usr/lib/aarch64-linux-gnu/qt6/plugins/platforms/libqwayland-generic.so”,target-name=“/usr/lib/aarch64-linux-gnu/qt6/plugins/platforms/libqwayland-generic.so”,host-name=“/usr/lib/aarch64-linux-gnu/qt6/plugins/platforms/libqwayland-generic.so”,symbols-loaded=“0”,thread-group=“i1”,ranges=[{from=“0x0000ffffb63c1550”,to=“0x0000ffffb63c19a0”}]

1: (3281) ->=library-loaded,id=“/lib/aarch64-linux-gnu/libQt6WaylandClient.so.6”,target-name=“/lib/aarch64-linux-gnu/libQt6WaylandClient.so.6”,host-name=“/lib/aarch64-linux-gnu/libQt6WaylandClient.so.6”,symbols-loaded=“0”,thread-group=“i1”,ranges=[{from=“0x0000ffffb6327a40”,to=“0x0000ffffb6373ca0”}]

1: (3281) ->=library-loaded,id=“/lib/aarch64-linux-gnu/libwayland-cursor.so.0”,target-name=“/lib/aarch64-linux-gnu/libwayland-cursor.so.0”,host-name=“/lib/aarch64-linux-gnu/libwayland-cursor.so.0”,symbols-loaded=“0”,thread-group=“i1”,ranges=[{from=“0x0000ffffb6291330”,to=“0x0000ffffb6292af8”}]

[Warning] 1: (3331) STDERR: Failed to create wl_display (No such file or directory)

[Warning] 1: (3371) STDERR: qt.qpa.plugin: Could not load the Qt platform plugin “wayland” in “” even though it was found.

[Warning] 1: (3371) STDERR: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

[Warning] 1: (3371) STDERR: Available platform plugins are: minimal, linuxfb, eglfs, wayland, xcb, vkkhrdisplay, minimalegl, wayland-egl, offscreen, vnc.

1: (3374) ->~“\nProgram”

1: (3374) ->~" received signal SIGABRT, Aborted.\n"

1: (3374) ->~“0x0000ffffbb0a2e90 in ?? () from /lib/aarch64-linux-gnu/libc.so.6\n”

1: (3374) ->*stopped,reason=“signal-received”,signal-name=“SIGABRT”,signal-meaning=“Aborted”,frame={addr=“0x0000ffffbb0a2e90”,func=“??”,args=,from=“/lib/aarch64-linux-gnu/libc.so.6”,arch=“aarch64”},thread-id=“1”,stopped-threads=“all”,core=“0”

Program received signal SIGABRT, Aborted.

0x0000ffffbb0a2e90 in ?? () from /lib/aarch64-linux-gnu/libc.so.6

ToradexAI · May 7, 2025, 5:06pm

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer?

Hello! Thank you for sharing your detailed logs.

The error message Failed to create wl_display (No such file or directory) and the Qt warning about not being able to load the “wayland” platform plugin typically indicate that your Qt application is trying to start with the Wayland backend, but the Wayland display server/compositor is not running or not accessible.

Here are steps you can take to resolve the issue:

Ensure the Wayland Compositor is Running
The error suggests your system does not have an active Wayland session or compositor. Ensure you are running a Wayland compositor (such as Weston) on your system. If you are running your application inside a container, make sure the container has access to the Wayland socket.
Related discussion
Verify Socket Permissions
The Wayland socket is usually located at /run/wayland-0. Ensure proper permissions for your application/user:
```
chmod 666 /run/wayland-0
```
This makes the display socket accessible to all users.
Reference
If Running in a Container – Device Access
If your application runs in a Docker or Podman container on Torizon, you must ensure the required device files are available. Pass the correct device rules:
- c 4:* rmw (tty devices)
- c 13:* rmw (input devices)
- c 199:* rmw (GPU access)
- c 226:* rmw (DRI devices)
  More details: Hardware Acceleration with Containers
Qt6 Applications – Clean Build
Sometimes, Qt platform plugin issues are due to improper installation or build mismatches. For Qt6, clear your build directory and rebuild the application to ensure all Qt6 libraries are properly integrated.
See advice here: Yocto with Qt6 build discussion
Alternatives:
- If you do not intend to use Wayland, consider running with the eglfs or linuxfb backend, passing -platform eglfs or -platform linuxfb to your Qt application.

If these steps do not resolve your issue, please provide additional details about your hardware, OS version, and how you launch your application (directly, via container, etc.).

Best regards,
Toradex AI Assistant.

analage · May 7, 2025, 5:31pm

failing to start the wetson container, below are the logs

docker logs torizon-weston-1
Switching VT tty1 to text mode if currently in graphics mode
Switching to VT 7
SoC is: ‘i.MX8MP’
SoC has GPU: true
SoC has DPU: false
g2d implementation: viv
Removing previously created ‘.X*-lock’ entries under /tmp before starting Weston. Pass ‘IGNORE_X_LOCKS=1’ environment variable to Weston container to disable this behavior.
dos2unix: converting file /etc/xdg/weston/weston.ini to Unix format…
dos2unix: converting file /etc/xdg/weston-dev/weston.ini to Unix format…
00:00:00.000 [INFO] [seatd/seat.c:39] Created VT-bound seat seat0
00:00:00.000 [INFO] [seatd/seatd.c:194] seatd started
Date: 2025-05-07 UTC
[16:57:36.994] weston 12.0.4
Build: 12.0.4
[16:57:36.994] Command line: weston -Bdrm-backend.so -Swayland-0 --use-g2d
[16:57:36.994] OS: Linux, 5.15.177-6.8.3-devel+git.5a6602cc6c32, #1-TorizonCore SMP PREEMPT Fri Mar 21 16:22:58 UTC 2025, aarch64
[16:57:36.994] Flight recorder: enabled
[16:57:36.995] Using config file ‘/etc/xdg/weston/weston.ini’
[16:57:36.995] Output repaint window is 7 ms maximum.
[16:57:36.995] Loading module ‘/usr/lib/aarch64-linux-gnu/libweston-12/drm-backend.so’
[16:57:37.002] initializing drm backend
[16:57:37.002] Trying libseat launcher…
00:00:00.019 [INFO] [seatd/server.c:145] New client connected (pid: 29, uid: 1000, gid: 1000)
00:00:00.019 [INFO] [seatd/seat.c:170] Added client 7 to seat0
00:00:00.019 [INFO] [seatd/seat.c:480] Opened client 7 on seat0
[16:57:37.003] [libseat/libseat.c:73] Seat opened with backend ‘seatd’
[16:57:37.003] [libseat/backend/seatd.c:212] Enabling seat
[16:57:37.003] libseat: session control granted
[16:57:37.008] using /dev/dri/card0
[16:57:37.009] DRM: supports atomic modesetting
[16:57:37.009] DRM: does not support GBM modifiers
[16:57:37.009] DRM: does not support async page flipping
[16:57:37.010] DRM: supports picture aspect ratio
[16:57:37.010] Loading module ‘/usr/lib/aarch64-linux-gnu/libweston-12/g2d-renderer.so’
g2d_open: fail with status -7
[16:57:37.025] g2d_open fail.
[16:57:37.025] g2d_renderer_create faile.
[16:57:37.025] failed to initialize g2d renderer
00:00:00.042 [INFO] [seatd/seat.c:418] No clients on seat0 to activate
00:00:00.043 [INFO] [seatd/seat.c:524] Closed client 7 on seat0
00:00:00.043 [INFO] [seatd/seat.c:192] Removed client 7 from seat0
00:00:00.044 [INFO] [seatd/client.c:471] Client disconnected
00:00:00.109 [INFO] [seatd/seatd.c:218] seatd stopped
Switching back to vt 1
Switching VT tty1 to text mode if currently in graphics mode
Switching to VT 7
SoC is: ‘i.MX8MP’
SoC has GPU: true
SoC has DPU: false
g2d implementation: viv
Removing previously created ‘.X*-lock’ entries under /tmp before starting Weston. Pass ‘IGNORE_X_LOCKS=1’ environment variable to Weston container to disable this behavior.
dos2unix: converting file /etc/xdg/weston/weston.ini to Unix format…
dos2unix: converting file /etc/xdg/weston-dev/weston.ini to Unix format…
00:00:00.000 [INFO] [seatd/seat.c:39] Created VT-bound seat seat0
00:00:00.000 [INFO] [seatd/seatd.c:194] seatd started
Date: 2025-05-07 UTC
[17:13:17.758] weston 12.0.4
https://wayland.freedesktop.org
Bug reports to: Making sure you're not a bot!
Build: 12.0.4
[17:13:17.758] Command line: weston -Bdrm-backend.so -Swayland-0 --use-g2d
[17:13:17.758] OS: Linux, 5.15.177-6.8.3-devel+git.5a6602cc6c32, #1-TorizonCore SMP PREEMPT Fri Mar 21 16:22:58 UTC 2025, aarch64
[17:13:17.758] Flight recorder: enabled
[17:13:17.758] Using config file ‘/etc/xdg/weston/weston.ini’
[17:13:17.759] Output repaint window is 7 ms maximum.
[17:13:17.759] Loading module ‘/usr/lib/aarch64-linux-gnu/libweston-12/drm-backend.so’
[17:13:17.766] initializing drm backend
[17:13:17.766] Trying libseat launcher…
00:00:00.018 [INFO] [seatd/server.c:145] New client connected (pid: 29, uid: 1000, gid: 1000)
00:00:00.018 [INFO] [seatd/seat.c:170] Added client 7 to seat0
00:00:00.018 [INFO] [seatd/seat.c:480] Opened client 7 on seat0
[17:13:17.767] [libseat/libseat.c:73] Seat opened with backend ‘seatd’
[17:13:17.767] [libseat/backend/seatd.c:212] Enabling seat
[17:13:17.767] libseat: session control granted
[17:13:17.773] using /dev/dri/card0
[17:13:17.773] DRM: supports atomic modesetting
[17:13:17.773] DRM: does not support GBM modifiers
[17:13:17.773] DRM: does not support async page flipping
[17:13:17.773] DRM: supports picture aspect ratio
[17:13:17.773] Loading module ‘/usr/lib/aarch64-linux-gnu/libweston-12/g2d-renderer.so’
g2d_open: fail with status -7
[17:13:17.784] g2d_open fail.
[17:13:17.784] g2d_renderer_create faile.
[17:13:17.784] failed to initialize g2d renderer
00:00:00.037 [INFO] [seatd/seat.c:418] No clients on seat0 to activate
00:00:00.037 [INFO] [seatd/seat.c:524] Closed client 7 on seat0
00:00:00.037 [INFO] [seatd/seat.c:192] Removed client 7 from seat0
00:00:00.037 [INFO] [seatd/client.c:471] Client disconnected
00:00:00.100 [INFO] [seatd/seatd.c:218] seatd stopped
Switching back to vt 1
Switching VT tty1 to text mode if currently in graphics mode
Switching to VT 7
SoC is: ‘i.MX8MP’
SoC has GPU: true
SoC has DPU: false
g2d implementation: viv
Removing previously created ‘.X*-lock’ entries under /tmp before starting Weston. Pass ‘IGNORE_X_LOCKS=1’ environment variable to Weston container to disable this behavior.
dos2unix: converting file /etc/xdg/weston/weston.ini to Unix format…
dos2unix: converting file /etc/xdg/weston-dev/weston.ini to Unix format…
00:00:00.000 [INFO] [seatd/seat.c:39] Created VT-bound seat seat0
00:00:00.000 [INFO] [seatd/seatd.c:194] seatd started
Date: 2025-05-07 UTC
[17:14:31.320] weston 12.0.4
Build: 12.0.4
[17:14:31.321] Command line: weston -Bdrm-backend.so -Swayland-0 --use-g2d
[17:14:31.321] OS: Linux, 5.15.177-6.8.3-devel+git.5a6602cc6c32, #1-TorizonCore SMP PREEMPT Fri Mar 21 16:22:58 UTC 2025, aarch64
[17:14:31.321] Flight recorder: enabled
[17:14:31.321] Using config file ‘/etc/xdg/weston/weston.ini’
[17:14:31.322] Output repaint window is 7 ms maximum.
[17:14:31.322] Loading module ‘/usr/lib/aarch64-linux-gnu/libweston-12/drm-backend.so’
[17:14:31.329] initializing drm backend
[17:14:31.329] Trying libseat launcher…
00:00:00.028 [INFO] [seatd/server.c:145] New client connected (pid: 29, uid: 1000, gid: 1000)
00:00:00.029 [INFO] [seatd/seat.c:170] Added client 7 to seat0
00:00:00.029 [INFO] [seatd/seat.c:480] Opened client 7 on seat0
[17:14:31.330] [libseat/libseat.c:73] Seat opened with backend ‘seatd’
[17:14:31.330] [libseat/backend/seatd.c:212] Enabling seat
[17:14:31.330] libseat: session control granted
[17:14:31.336] using /dev/dri/card0
[17:14:31.336] DRM: supports atomic modesetting
[17:14:31.336] DRM: does not support GBM modifiers
[17:14:31.336] DRM: does not support async page flipping
[17:14:31.336] DRM: supports picture aspect ratio
[17:14:31.337] Loading module ‘/usr/lib/aarch64-linux-gnu/libweston-12/g2d-renderer.so’
g2d_open: fail with status -7
[17:14:31.349] g2d_open fail.
[17:14:31.349] g2d_renderer_create faile.
[17:14:31.349] failed to initialize g2d renderer
00:00:00.048 [INFO] [seatd/seat.c:418] No clients on seat0 to activate
00:00:00.048 [INFO] [seatd/seat.c:524] Closed client 7 on seat0
00:00:00.048 [INFO] [seatd/seat.c:192] Removed client 7 from seat0
00:00:00.049 [INFO] [seatd/client.c:471] Client disconnected
00:00:00.113 [INFO] [sea

lucas_az.tx · May 8, 2025, 1:42pm

Hi @analage!

Whenever you create a new topic in our community, please use as much detail about your problem as possible, not only the logs. With a detailed description of the issue, we can provide you a better and faster support.

Could you detail what steps you took and what you were expecting with them?

Best regards.

analage · May 8, 2025, 2:08pm

Hi Lucas,

I am creating my first test application using Torizon IDE extension, project template I have selected is C++ QT QML. When I try to run the application, it throws an unknown error occurred exception

I have not modified any configuration, I selected the template and once project is created, I am trying to run it and see if I can get the Hello Torizon displayed on UI.

On the SBC I flashed an image using easy installer. The image I selected was TorizonCore with ver6.8.2 with no containers. If I install any other image, then I am not able to find the SBC. Did I selected a correct image to install on SBC?

I tried manually installing the weston container and running the sample application inside container on the board but that also fails.

I tried to run the test app with offscreen option, then it runs but running with wayland/xcb/linuxfb all options fail.

lucas_az.tx · May 8, 2025, 2:20pm

Hi @analage!

Which module and carrier board are you using?

Best regards.

analage · May 8, 2025, 2:34pm

Hi Lucas,

I am using Verdin iMX8MP, Yavia board.

lucas_az.tx · May 8, 2025, 3:52pm

Hi @analage!

I talked to our IDE team, and they said that the default Torizon version for the templates right now is 7. So I would suggest you reinstall a reference image, but in version 7, and test it again.

Best regards.

analage · May 8, 2025, 6:11pm

Hi Lucas,

Thanks, could you please guide me on the exact image name and version? While using the easy installer I can see multiple images with version 7.2 or 7.3 with names as Torizon OS, Torizon OS with Easy Pairing, Linux Embedded OS with Multimedia. etc. Which one I have to use?

Also, could you please help with any documentation link where I can read what is the difference between all the listed options on the easy installer and which one to choose while working with IDE?