Unable to run GUIs

Technical Support
,
1

I have a new IMX8MP SoM and Mallow carrier card and have been unsuccessful in using any graphical containers. I have been trying to run this example: https://developer.toradex.com/torizon/application-development/use-cases/gui/web-browser-kiosk-mode-with-torizoncore/#imx8. When I try to run the following command to start Weston/Wayland, nothing happens on the ASUS FHD monitor that is hooked up via the HDMI port on the Mallow board.

docker container run -d --name=weston --net=host \
    --cap-add CAP_SYS_TTY_CONFIG \
    -v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ \
    --device-cgroup-rule="c 4:* rmw" --device-cgroup-rule="c 253:* rmw" \
    --device-cgroup-rule="c 13:* rmw" --device-cgroup-rule="c 226:* rmw" \
    --device-cgroup-rule="c 10:223 rmw" --device-cgroup-rule="c 199:0 rmw" \
    torizon/weston-imx8:4 \
    --developer

Swapping out the -d for -it here is the output of the program.

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  [seatd/seat.c:39] Created VT-bound seat seat0
00:00:00.000  [seatd/seatd.c:194] seatd started
Date: 2024-12-11 UTC
[00:09:08.783] weston 12.0.4
               https://wayland.freedesktop.org
               Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
               Build: 12.0.4
[00:09:08.783] Command line: weston -Bdrm-backend.so --current-mode -Swayland-0 --use-g2d
[00:09:08.783] OS: Linux, 6.6.23-7.0.0-g558ba3740880, #1-Torizon SMP PREEMPT Wed Sep 25 11:25:16 UTC 2024, aarch64
[00:09:08.783] Flight recorder: enabled
[00:09:08.783] Using config file '/etc/xdg/weston-dev/weston.ini'
[00:09:08.784] Output repaint window is 7 ms maximum.
[00:09:08.784] Loading module '/usr/lib/aarch64-linux-gnu/libweston-12/drm-backend.so'
[00:09:08.792] initializing drm backend
[00:09:08.792] Trying libseat launcher...
00:00:00.023  [seatd/server.c:145] New client connected (pid: 29, uid: 1000, gid: 1000)
00:00:00.024  [seatd/seat.c:170] Added client 7 to seat0
00:00:00.024  [seatd/seat.c:480] Opened client 7 on seat0
[00:09:08.794] [libseat/libseat.c:73] Seat opened with backend 'seatd'
[00:09:08.794] [libseat/backend/seatd.c:212] Enabling seat
[00:09:08.794] libseat: session control granted
[00:09:08.798] using /dev/dri/card1
[00:09:08.798] DRM: supports atomic modesetting
[00:09:08.798] DRM: does not support GBM modifiers
[00:09:08.798] DRM: does not support async page flipping
[00:09:08.798] DRM: supports picture aspect ratio
[00:09:08.799] Loading module '/usr/lib/aarch64-linux-gnu/libweston-12/g2d-renderer.so'
[00:09:08.949] event1  - gpio-keys: is tagged by udev as: Keyboard
[00:09:08.950] event1  - gpio-keys: device is a keyboard
[00:09:08.954] event0  - 30370000.snvs:snvs-powerkey: is tagged by udev as: Keyboard
[00:09:08.954] event0  - 30370000.snvs:snvs-powerkey: device is a keyboard
[00:09:08.961] event3  - LITEON Technology USB Multimedia Keyboard: is tagged by udev as: Keyboard
[00:09:08.961] event3  - LITEON Technology USB Multimedia Keyboard: device is a keyboard
[00:09:09.035] event4  - USB Optical Mouse: is tagged by udev as: Mouse
[00:09:09.035] event4  - USB Optical Mouse: device is a pointer
[00:09:09.039] event2  - audio-hdmi HDMI Jack: is tagged by udev as: Switch
[00:09:09.129] event2  - not using input device '/dev/input/event2'
[00:09:09.160] libinput: configuring device "gpio-keys".
[00:09:09.160] libinput: configuring device "30370000.snvs:snvs-powerkey".
[00:09:09.160] libinput: configuring device "LITEON Technology USB Multimedia Keyboard".
[00:09:09.160] libinput: configuring device "USB Optical Mouse".
[00:09:09.161] DRM: head 'HDMI-A-1' found, connector 38 is disconnected.
[00:09:09.273] DRM: head 'HDMI-A-2' found, connector 40 is connected, EDID make 'ACI', model 'ASUS VE278', serial 'J6LMTF110985'
               Supported EOTF modes: SDR
[00:09:09.274] Registered plugin API 'weston_drm_output_api_v1' of size 40
[00:09:09.274] Registered plugin API 'weston_drm_virtual_output_api_v2' of size 48
[00:09:09.274] Color manager: no-op
[00:09:09.274] Module '/usr/lib/aarch64-linux-gnu/libgbm.so' already loaded
[00:09:09.274] Output 'HDMI-A-2' attempts EOTF mode: SDR
[00:09:09.274] Output 'HDMI-A-2' using color profile: built-in default sRGB SDR profile
[00:09:09.282] Output HDMI-A-2 (crtc 36) video modes:
               1920x1080@60.0, preferred, current, 148.5 MHz
               1920x1080@60.0 16:9, 148.5 MHz
               1920x1080@59.9 16:9, 148.4 MHz
               1920x1080@50.0 16:9, 148.5 MHz
               1680x1050@59.9, 119.0 MHz
               1280x1024@75.0, 135.0 MHz
               1280x1024@60.0, 108.0 MHz
               1440x900@59.9, 88.8 MHz
               1280x960@60.0, 108.0 MHz
               1152x864@75.0, 108.0 MHz
               1280x720@60.0, 74.2 MHz
               1280x720@60.0 16:9, 74.2 MHz
               1280x720@59.9 16:9, 74.2 MHz
               1280x720@50.0, 74.2 MHz
               1280x720@50.0 16:9, 74.2 MHz
               1440x576@50.0 4:3, 54.0 MHz
               1440x576@50.0 16:9, 54.0 MHz
               1024x768@75.0, 78.8 MHz
               1024x768@70.1, 75.0 MHz
               1024x768@60.0, 65.0 MHz
               1440x480@60.0 4:3, 54.1 MHz
               1440x480@60.0 16:9, 54.1 MHz
               1440x480@59.9 4:3, 54.0 MHz
               1440x480@59.9 16:9, 54.0 MHz
               832x624@74.6, 57.3 MHz
               800x600@75.0, 49.5 MHz
               800x600@72.2, 50.0 MHz
               800x600@60.3, 40.0 MHz
               800x600@56.2, 36.0 MHz
               720x576@50.0, 27.0 MHz
               720x576@50.0 4:3, 27.0 MHz
               720x576@50.0 16:9, 27.0 MHz
               720x480@60.0 4:3, 27.0 MHz
               720x480@60.0 16:9, 27.0 MHz
               720x480@59.9, 27.0 MHz
               720x480@59.9 4:3, 27.0 MHz
               720x480@59.9 16:9, 27.0 MHz
               640x480@75.0, 31.5 MHz
               640x480@66.7, 30.2 MHz
               640x480@60.0 4:3, 25.2 MHz
               640x480@59.9, 25.2 MHz
               640x480@59.9 4:3, 25.2 MHz
               720x400@70.1, 28.3 MHz
[00:09:09.283] associating input device event1 with output HDMI-A-2 (none by udev)
[00:09:09.283] associating input device event0 with output HDMI-A-2 (none by udev)
[00:09:09.283] associating input device event3 with output HDMI-A-2 (none by udev)
[00:09:09.283] associating input device event4 with output HDMI-A-2 (none by udev)
[00:09:09.283] Output 'HDMI-A-2' enabled with head(s) HDMI-A-2
[00:09:09.283] Compositor capabilities:
               arbitrary surface rotation: yes
               screen capture uses y-flip: yes
               cursor planes: yes
               arbitrary resolutions: no
               view mask clipping: yes
               explicit sync: yes
               color operations: no
               presentation clock: CLOCK_MONOTONIC, id 1
               presentation clock resolution: 0.000000001 s
[00:09:09.284] Loading module '/usr/lib/aarch64-linux-gnu/weston/desktop-shell.so'
[00:09:09.285] Loading module '/usr/lib/aarch64-linux-gnu/libweston-12/xwayland.so'
[00:09:09.319] Registered plugin API 'weston_xwayland_v1' of size 32
[00:09:09.319] Registered plugin API 'weston_xwayland_surface_v1' of size 16
[00:09:09.319] xserver listening on display :0
[00:09:09.319] Loading module '/usr/lib/aarch64-linux-gnu/weston/screen-share.so'
[00:09:09.321] launching '/usr/lib/aarch64-linux-gnu/weston-keyboard'
[00:09:09.329] launching '/usr/lib/aarch64-linux-gnu/weston-desktop-shell'
[00:09:09.338] atomic: couldn't commit new state: Invalid argument
[00:09:09.338] repaint-flush failed: Invalid argument
could not load cursor 'dnd-move'
could not load cursor 'dnd-move'
could not load cursor 'dnd-copy'
could not load cursor 'dnd-copy'
could not load cursor 'dnd-none'
could not load cursor 'dnd-none'

It gives a vague error about an invalid argument that I can’t find anything about online.

The subsequent call to Chromium gives this output:

sudo docker run -it --rm --name=chromium     -v /tmp:/tmp -v /var/run/dbus:/var/run/dbus     -v /dev/galcore:/dev/galcore --device-cgroup-rule='c 199:* rmw'     --security-opt seccomp=unconfined --shm-size 256mb     torizon/chromium-imx8:$CT_TAG_CHROMIUM     --virtual-keyboard --user-data-dir=/tmp https://www.toradex.com
[7:32:1211/002616.475456:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[7:32:1211/002616.476305:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[7:32:1211/002616.476455:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[7:32:1211/002616.476555:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[7:32:1211/002616.476647:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
*** stack smashing detected ***: terminated
[7:32:1211/002616.574887:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
*** stack smashing detected ***: terminated
[7:32:1211/002616.776192:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[7:32:1211/002616.776323:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[7:7:1211/002616.967306:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=134
*** stack smashing detected ***: terminated
[7:7:1211/002616.981898:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: 
*** stack smashing detected ***: terminated
[7:75:1211/002617.064437:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[7:75:1211/002617.066216:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[7:75:1211/002617.067646:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[7:7:1211/002617.070771:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=134
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[7:7:1211/002617.181840:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=134
[7:7:1211/002617.181954:FATAL:gpu_data_manager_impl_private.cc(423)] GPU process isn't usable. Goodbye.
*** stack smashing detected ***: terminated
Trace/breakpoint trap (core dumped)

Software Summary

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           6.6.23-7.0.0-g558ba3740880 #1-Torizon SMP PREEMPT Wed Sep 25 11:25:16 UTC 2024
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/4c71f4b269116eb0916ec8ec0e61598a04c7107cb2167a9a135d502754692b96/0
Distro name:              NAME="Torizon OS"
Distro version:           VERSION_ID=7.0.0-build.1
Hostname:                 verdin-imx8mp-15207913
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Plus WB on Verdin Development Board
Toradex version:          0070 V1.1A
Serial number:            15207913
Processor arch:           aarch64
------------------------------------------------------------
2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello,

I’m sorry to hear you’re having trouble with running graphical containers on your iMX8MP SoM and Mallow carrier card. Let’s address the issues step by step:

  1. Weston Not Displaying on Monitor:

    • The error message “atomic: couldn’t commit new state: Invalid argument” suggests a potential issue with the display configuration. Ensure that your HDMI cable is securely connected and that the monitor is set to the correct input source.
    • Check the weston.ini configuration file to ensure the [output] section is correctly set up for your HDMI display. You may need to specify the correct resolution and refresh rate.
    • Verify that your TorizonCore version and kernel are compatible with the Weston version you are using. Updating to the latest TorizonCore release might help resolve compatibility issues.

  2. Chromium Errors:

    • The errors related to “Failed to connect to the bus” and “stack smashing detected” indicate issues with D-Bus communication and possibly memory corruption.
    • Ensure that the D-Bus service is running correctly on your system. You can check this by running systemctl status dbus on the host.
    • Make sure the container has the necessary permissions to access D-Bus. This is typically done by mounting /var/run/dbus and using the --net=host option, which you have already included.
    • Consider increasing the shared memory size (--shm-size) if Chromium is running out of memory.

I hope these suggestions help you resolve the issues. If you have further questions, feel free to ask.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Easy Installer problem on AM62 D, IT with Mallow V1.1 board.

3

Greetings @allen.morrison,

I just checked and I was able to reproduce the issue with the Weston container. Specifically it seems to be an issue on just the native HDMI. If i use a different carrier board with DSI-to-HDMI, then it works on that interface. Let me report this to our team.

For the Chromium issue, currently there are known issues and instabilities with Chromium on Torizon OS 7.X versions.

In the meantime if you don’t mind I would recommend trying Torizon OS 6.8.0. These should work on that version. Just make sure to reference the right version of our developer site documentation when using Torizon OS 6.8.0, there should be an option in the upper right corner of our developer site to change the documentation version.

Best Regards,
Jeremias

4

I greatly appreciate the quick support and path forward Jeremias! Tomorrow I’ll try to re-flash the board and start the Weston container.
Let me know if there is anything you need from me or if I can track the resolution of the issue in Torizon OS 7.x and I’ll gladly subscribe.

5

Let me know if there is anything you need from me or if I can track the resolution of the issue in Torizon OS 7.x and I’ll gladly subscribe.

For now I believe we already have all the needed information for these issues. Also I just learned the issue with Torizon OS 7.X Weston on native HDMI with Verdin i.MX8M Plus is also a known issue at this time.

Given that, I would suggest to just start with 6.8.0 for now as I said before. In honesty, we just started on the 7.X series which introduced a lot of major breaking changes. Meaning, at this time it’s kind of expected that the 6.X series would be in a more stable position given that it has had ~2 years to mature.

Best Regards,
Jeremias

6

I appreciate the honesty and support. Moving back to Torizon OS v6.8.0 allowed me to successfully start up the Weston and Chromium containers and continue testing. Many thanks Jeremias!

7

Glad I was able to assist!