Errors launching chromium-imx8 on Torizon OS 7

Technical Support
, , , ,
1

I’ve just tried Torizon OS 7 7.1.0-devel-20241101+build.88 with torizon/weston-imx8:stable:rc and torizon/chromium-imx8:stable:rc.
When chromium starts it prints the following errors on the command line console

kiosk-1   | [8:33:1104/090517.736571: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")
kiosk-1   | [8:33:1104/090517.736943: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")
kiosk-1   | [8:33:1104/090517.737070: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")
kiosk-1   | [8:33:1104/090517.737152: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")
kiosk-1   | [8:33:1104/090517.737207: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")
kiosk-1   | [8:33:1104/090517.829571: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")
kiosk-1   | [8:33:1104/090517.830348: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")
kiosk-1   | [8:90:1104/090518.057966: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
kiosk-1   | [8:90:1104/090518.061169: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
kiosk-1   | [8:90:1104/090518.065772: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
kiosk-1   | [8:29:1104/090518.336566: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")
kiosk-1   | [8:29:1104/090518.336669: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")
kiosk-1   | [8:8:1104/090518.644842:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
kiosk-1   | [8:8:1104/090518.644927:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
kiosk-1   | [8:29:1104/090518.645174: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")
kiosk-1   | [8:8:1104/090518.665487:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
kiosk-1   | [8:30:1104/090518.670375: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")
kiosk-1   | [8:8:1104/090518.676642:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
kiosk-1   | [8:30:1104/090518.678403: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")
kiosk-1   | [8:8:1104/090518.680734:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
kiosk-1   | [8:30:1104/090518.681061: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")
kiosk-1   | [56:116:1104/090518.678634:ERROR:v4l2_utils.cc(578)] Could not open /dev/video-dec0: No such file or directory (2)
kiosk-1   | [56:116:1104/090518.682459:ERROR:v4l2_utils.cc(578)] Could not open /dev/video-dec0: No such file or directory (2)
kiosk-1   | [8:8:1104/090518.685599:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
kiosk-1   | [8:30:1104/090519.439983:ERROR:cert_issuer_source_aia.cc(35)] Error parsing cert retrieved from AIA (as DER):
kiosk-1   | ERROR: Couldn't read tbsCertificate as SEQUENCE
kiosk-1   | ERROR: Failed parsing Certificate
kiosk-1   |
kiosk-1   | [57:86:1104/090519.532185:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -202

I can see that chromium is shown on the screen and seems working (more or less).
Are the above errors a known behavior?

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:

Yes, the errors you are encountering when launching Chromium on Torizon OS 7 are known behaviors. These errors are primarily related to D-Bus connectivity and SSL issues, as detailed in the context provided. The errors such as “Failed to connect to the bus” and “Failed to call method” indicate potential misconfigurations or missing D-Bus services, which are essential for inter-process communication. Additionally, the SSL handshake errors suggest problems with SSL certificate handling, which could affect secure connections.

To address these issues, it is advisable to:

  1. Investigate the D-Bus configuration to ensure that the necessary services are running and properly configured.
  2. Check for proper device access, especially for video devices if applicable.
  3. Ensure that SSL certificates are correctly handled and configured.

These steps should help improve the performance and reliability of Chromium on Torizon OS 7.

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

GPU performance in Chromium container on Torizon OS iMX8M-Plus.

5

Hi @vix !

Thanks for bringing this up.

I am not sure about the specific issue you are facing, but the chromium container in general is currently not yet stable/available for i.MX8, i.MX7 and i.MX6, as we can see from Release 4.0.0 · torizon/torizon-containers · GitHub. So it is safe to say that your are facing a known issue.

Best regards,

6

Hi @vix !

Do you have any updates regarding this topic?

Best regards,

7

Hi @henrique.tx

the same issue even on the new 4.1.1 containers.
To be honest, I’ve been waiting for a feedback from Toradex side (when the 4.x containers are stable).

8

Hello @vix,

The work on the 4.x containers is ongoing.

The Weston container is ready and can leverage the GPU for the Verdin iMX8MP.
I am also closely following the progress on the Chromium container, so when it is ready I will send an update here.

Best Regards,
Bruno