we’ve been working with the same application since TC 5.5.0 and we hadn’t identified that problem before
I see you’re now on 6.5.0. Did you only start seeing this issue when transitioning to this newer version of the OS?
Looking at your Weston logs I see one major difference between the “ok” and “bad” state. In the “bad” state it looks like XWayland never starts, these logs are missing in the “bad” state but are present in the “ok” state:
...
[17:32:59.751] Loading module '/usr/lib/aarch64-linux-gnu/libweston-9/xwayland.so'
[17:32:59.874] Registered plugin API 'weston_xwayland_v1' of size 32
[17:32:59.875] Registered plugin API 'weston_xwayland_surface_v1' of size 16
[17:32:59.877] xserver listening on display :0
...
[17:33:01.105] Spawned Xwayland server, pid 47
[ 1] wl_drm_is_format_supported, format = 0x30335241
[ 2] wl_drm_is_format_supported, format = 0x30335258
[ 3] wl_drm_is_format_supported, format = 0x30334241
[ 4] wl_drm_is_format_supported, format = 0x30334258
Disabling glamor and dri3 support, XWAYLAND_NO_GLAMOR is set
Failed to initialize glamor, falling back to sw
[17:33:01.273] xfixes version: 5.0
[17:33:01.297] created wm, root 71
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 569, clipping.
> X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
If your application relies on X then not having XWayland running would be problematic indeed.
Looking at your docker-compose.yml I noticed based on the way you’re starting the weston-vivante container that this must using the 2/bullseye tag for this container. Is that correct?
If that is the case could you adapt to instead use the 3/bookworm tag. Our 2/bullseye based containers were designed and optimized to run on Torizon OS 5.X. While they can run on 6.X it is much more preferable to use the 3/bookworm based containers instead. As these containers were designed and optimized to be used on 6.X. Perhaps this might be the issue itself.
Please try using the 3/bookworm based weston-vivante container instead and let me know if the issue still appears. Be aware that this newer version of the container requires slightly different arguments to be launched, you can’t just use the same arguments as you’ve been using. You can see in many of our articles like this: Debian Containers for Torizon | Toradex Developer Center
To see how to launch the 3/bookworm based weston-vivante container.
Best Regards,
Jeremias