Torizon OS Issue Tracker

Description: U-Boot fails with the error "collect2: error: ld returned 1 exit status" when building a signed Torizon OS image for Verdin iMX8M Mini.

Update: this is fixed, use Torizon OS 6.6.0-devel-202402 or newer.

Description: On TorizonCore 6, the splash screen is not being displayed on Verdin iMX8M Mini and Verdin iMX8M Plus.

Description: Due to the Docker daemon starting too early in the boot process, before the usermount service that mounts the external storage, sometimes the Docker data on external storage failed to boot the board and led to an infinite reboot loop.

Description: In TorizonCore 6, it is not possible to connect to a Toradex SoM with on-SoM Wi-Fi configured in Access Point (AP) mode. When configuring the device in AP mode, no errors are displayed.

Description: Offline sync updates are not working on TorizonCore 6. Even though both OS and application updates are installed, the process is never concluded and after the reboot with the new OS version, the application is never started.

Update: this bug has been fixed. As a side-effect, in case a rollback happens during a synchronous offline update, the newer application container image is not removed from the system, as it should. This means that some of the flash storage space will be used without need.

Description: The boot time on TorizonCore 6 for 32-bit devices has increased by approximately 2x.

Update: the root cause of the increased boot time seems to be that our Embedded Linux BSP 6 is using 2x CPU when compared with BSP 5.

Update 2: the BSP performance has been fixed. Despite that, TorizonCore first boot time seems to be greater on TorizonCore 6 than 5, so we continue to investigate it.

Description: Once a synchronous update is triggered, the new application is not expected to start until the system reboots and the new OS version is available. On this bug, which affects TorizonCore 6.x releases only, the application starts on the upcoming polling for updates (which by default is 5 minutes) regardless of whether the system reboots and the new OS is loaded.

Given the TorizonCore default polling of 5 minutes and that usually, a reboot due to a synchronous update happens before that time, this bug should not affect most customer use cases. If you customize TorizonCore to use a much shorter polling time, there might be a case when this undesired behavior happens.

Description: Although unsupported on TorizonCore 5, Bluetooth has been reportedly working on Verdin iMX8M Plus V1.0. It does not work on Verdin iMX8M Plus V1.1A, though.

We plan to add basic Bluetooth support only on TorizonCore 6 or newer, without testing any specific Bluetooth profile in particular.

Description: The Colibri Evaluation Board uses the SPI interface for an SPI-to-CAN controller, however, we do enable the spidev (a userspace SPI API) on the same SPI interface and CS with an overlay that is currently enabled by default. This leads to a conflict.

Starting from BSP 6.1.0, the overlay that enables spidev on the given SPI interface is not loaded by default. Our test infrastructure caught this change as a possible issue due to a missing symlink to "/dev/colibri-spi-cs0". In fact, this was the intended behavior after the change.

As a customer, if you want to use such an interface with spidev, you must disable the CAN and enable the spidev overlay. For more details on CAN and SPI in our BSP, refer to the CAN (Linux) and the SPI (Linux) articles. To manage device tree and overlays on TorizonCore, we recommend the articles Device Tree Overlays on Torizon and TorizonCore Builder Tool - Customizing TorizonCore Images.

Description: Secure offline updates only support a physical medium for updates - an SD Card or a USB stick. That said, the following unhandled exception was reported when someone tried the unsupported use case of NFS storage instead of a physical medium: "Aktualizr::RunForever exiting: boost::filesystem::status: No such device: "/nfs/update"".

This error might also affect supported use cases, for instance, if the physical medium does not behave as expected. Therefore we are working on fixing it.

Description: The pluggable media such as SD Card and USB Stick are meant to be mount at "/media/label", but sometimes it is mount at "/media/root/label".

Description: The package "python3-criptography" fails to build on kirkstone, apparently due to our patch.

We don't use this package on TorizonCore at the moment, but if you are doing a custom build that adds it either explicitly or as a dependency, your build will fail.

Update: the patch has been dropped.

Description: On Colibri iMX6ULL, two warnings were seen when running "docker info": "WARNING: No swap limit support" and "WARNING: No cpuset support". We will enable the SWAP configuration in the kernel, and cpuset is expected since this is a single-core CPU.

Description: The rngd.service fails to start on Verdin iMX8M Plus, which may lead to a slower boot.

Update: this was fixed at the BSP level for release 6.0.0, therefore this ticket has been rejected.

Description: On automated tests for our monthly pre-release, some symlinks to devices were missing. The missing ones are "/dev/colibri-spi-cs0" and "/dev/apalis-spi1-cs0", and they prevent the test from running through and checking other symlinks.

Update: this was fixed on the BSP level, nothing was required or done on TorizonCore.

Workaround: Test it on a nightly that has been released after the 6.0.0-devel-202209 monthly. Alternatively, if you plan to use the monthly, then access the given device directly, not though the symlink.

Description: The Colibri iMX7 boot hangs during the kernel startup.

Update: this was fixed at the BSP level, so nothing was done on TorizonCore. Use a nightly image from September 30 or newer to get the fix.

Description: Every time the "setup-environment" script is run, it automatically appends data to "auto.conf", making it inconvenient to use it.

Description: Colibri iMX7 has two watchdog sources: the SoC and the PMIC. BSP 5 uses the PMIC watchdog as "/dev/colibri-watchdog", which in turn is the one used by TorizonCore. It turns out that the watchdog firmware for the PMIC on BSP 5 is not as featureful as required to ensure the "shutdown" properly works.

Description: The Chromium and Cog containers were split, and HW acceleration on the GPU (rendering) enabled on Chromium. These changes have broken the startup of Portainer in our "TorizonCore with Evaluation Containers" image.

Description: The error "Top level object in '/var/sota/storage/docker-compose/docker-compose.yml.tmp' needs to be an object not ''." shows up in rare occasions, due to power cut on secondary updates leading to an empty /var/sota/storage/docker-compose/docker-compose.yml.tmp file. This leads to a scenario where the board cannot recovery from updates in the web UI and thus leads to a state where application updates cannot be performed anymore.

We are fixing it by making the file creation operation atomic, so it properly fails and rolls back if the file is not populated with the expected content during a power cut.

Description: The error "docker: Error response from daemon: transport is closing: unavailable." was identified by our test infrastructure on some SoMs, as Colibri iMX6ULL, Colibri iMX7, and Apalis iMX6D 1GB IT. We are investigating why.

If you experience the same error, please report it in our community website.

Update: we have downgraded from docker-moby 20.x to docker-ce 19.03.14, which is proven to be stable from our previous releases and test cases.

Description: During our internal tests to validate the secure offline updates implementation, we have noticed that synchronous updates don't work.

Description: The Weston configuration file does not make changes as expected. This was identified when trying to rotate the screen by 90 degrees, as documented in Working with Weston on TorizonCore.

Workaround: We suspect this is an issue with sharing the configuration file with the Weston container. Try to share the entire directory where the configuration file is located, instead of only the file itself. For example: "-v ${PWD}/weston/:/etc/xdg/weston" or "-v ${PWD}/weston-dev/:/etc/xdg/weston-dev"

Update 1: It seems that the underlying culprit are trailing whitespaces. Ensure that your configuration file does not contain trailing whitespace.

Update 2: in the end, the "name=*" line of the configuration file was commented out. Please remember to uncomment this line to make your customization effective.

Description: The current default "weston.ini" provided in our Debian containers has a trailing space in the commented line "#[output]". If this line is uncommented, a silent error happens due to the file being considered malformed.

Workaround: Remove the trailing whitespace manually.

Description: On development PCs with newer versions of Git that address CVE-2022-24765 and CVE-2022-24767, the TorizonCore build with Yocto Project/OpenEmbedded fails.

Workaround: This is fixed on commit 256b379f02da66522eb20d93071f95b9bd859f8e, update your local version of meta-toradex-torizon to this commit or newer.

Description: Our CI test infrastructure caught a regression on automounting a USB stick. This is due to the fact that, if a drive without a partition table is inserted during boot, it is not mounted properly. On hotplug, it does work as expected.

Description: The persistent journald logging should work, as it has been tested in the past. The feature was reported as not working in our community, therefore we are investigating and fixing it.

Update: the documentation is updated and the reported issue is fixed.

Description: Every time we release a TorizonCore version (quarterly or LTS) we test Qt using different back-ends, including the "linuxfb". We have noticed that, after running a Qt app with this back-end, it is not possible anymore to access the device via VNC/RDP, and a reboot is required.

Our latest findings show that the problem is due to the app leaving the TTY stuck in "graphics" mode instead of returning to "text" mode after the exit of the program. We are investigating how to ensure the TTY is returned to the "text" mode before an application is restarted.

Workaround: For this specific sample, if you exit it by pressing "Ctrl+Q" or "Right click --> Quit", it will properly return the TTY to "text" mode as to not let the error happen again. We are still evaluating why it happens, though.

In general, if you need VNC/RDP access, run your Qt app with either the Wayland or the EGLFS/KMS back-end for the moment.

Update: we have added a script to the weston Debian container to make sure the terminal is always reset to a usable state. This should fix the issue while being transparent to you.

Description: TorizonCore is failing to build in the plymouth's do_fetch task. The reason is that the upstream project renamed the master branch to main.

Description: The rngd service is failing on Colibri iMX6ULL eMMC because there is no entropy source (that is because iMX6ULL doesn’t have the CAAM module).

Description: The aktualizr-torizon project fails to compile outside of Yocto builds (i.e. when built manually).

Description: There is an issue when running neofetch inside Torizon's Debian-based containers, where Torizon's logo is not showed.

Description: On Colibri iMX6ULL, we cannot deploy custom images generated by TorizonCore Builder.

Edit: in the end, we have identified this an issue related to OSTree and U-Boot, and have fixed it with a patch in our OpenEmbedded layer meta-toradex-torizon. No changes were applied to TorizonCore Builder.

Description: After stopping the Weston container, the console screen is not displayed on the connected display. It is just blank instead.

Description: conmon fails to build because the upstream project renamed the master branch to main.

Description: The project git://github.com/coreos/go-systemd.git has renamed their master branch to main. Due to that, the build fails.

Description: When updating Verdin iMX8MM from TorizonCore 5.1.0 (quarterly release ) to TorizonCore 5.3.0 (nightly build), the boot fails with a "device tree not found" error.

Description: After updating to version 88.0.4324, Chromium doesn't start in fullscreen anymore.

Description: On each execution a new .X*-lock entry is created under /tmp and XWayland keeps incrementing X display number, this generates issues for any X-based application.

Description: The repo tool has been changed a while ago to create the manifest file as a plain xml file instead of a symlink. This was causing an issue where use-head-next was being added to MACHINEOVERRIDES even on monthly/quarterly builds, causing TorizonCore builds to build from the latest u-boot/kernel trees.

Description: The imx-gpu-viv-demos package installation is failing with dependencies issues.

Description: Following the gstreamer article, the demo fails on iMX7 with "/dev/video2: no such file or directory".

Description: TorizonCore reboots indefinitely if the docker service fails. This should only happen if the system is executing an update.

Description: It seems like QApplication which is used for Widgets does not support automatic translation of touch events to mouse events. That leads to touchscreen not working with QTWidgets applications.

Description: When doing a bad update, the rollback feature is not working as expected.

Description: The rngd service is failing on Colibri iMX6ULL.

Description: TorizonCore should be able to apply overlays using the overlays.txt implementation of the BSP.

Description: There is no weston-touch-calibrator for bullseye yet. We don’t need to compile weston-touch-calibrator as we had to for buster but we still need to add the special init file which exposes the touch API.

Description: Debian base container does not start the shell when run with no args.

Description: CONFIG_IGB is not enabled in mainline-based modules.

Description: A bug is preventing containers from being updated if there is no /var/sota/storage/docker-compose/docker-compose.yml file.

Description: Missing UPSTREAM in in the name of mainline-based images with preprovisioned containers

Description: The automount feature of USB Sticks does not work after a reboot. It only mounts on unplug/plug events.

Description: Torizoncore does not ask for end user to set up a new password any more at the first boot.

Description: There is not a way to invoke a browser in Kiosk and Full-Screen mode running on Torizon and Colibri iMX7D 1GB

Description: There is a limitation in the CAAM driver initialization that prevents the CAAM module to initialize properly when running in the non-secure world. To prevent systemd from showing that the service has failed (see below), let’s disable this service for iMX7 devices.

Description: Since we use reproducible builds, time stamps are set to 0.

Description: PWM sample container fail while building for arm64

Description: ADC sample container fail while building an image for arm64v8

Description: Make users and groups IDs stable in TorizonCore.

Description: Version number should be consistent throughout a TorizonCore image

Description: Kiosk container is not working in sht31 and grafana sample.

Workaround: add this to the docker-compose file: security_opt: - seccomp:unconfined

Description: Error in the comment about how to accept EULA required to run imx8 vivante graphic drivers.

Description: Added git to SDK cross-compilation toolchain containers

Description: Error when trying to install qt5-default: trying to overwrite '/usr/lib/aarch64-linux-gnu/libGL.so.1', which is also in package libgl1:arm64 1.1.0-1.

Description: Fixes a bug that was preventing i2c-tools from been installed inside a Debian container.

Description: Containers started via docker-compose can't be stopped via 'systemctl stop docker-compose.service'

Description: The mwifiex.conf file is missing in /etc/modprobe.d/, therefore it is not possible to use the WiFi interface in access point mode.

Workaround: Create the file on your own with the following content: 'options mwifiex driver_mode=0x3'

Description: Using `torizon/arm64v8-debian-wayland-base-vivante` it's not possible to install `libvulkan-vivante1` due to dependency error.

Description: After open Visual Studio with the plugin installed, I can succesfully build and debug a new project. However, after terminate the first debug session, the "Rebuild Torizon Application" button become grayed out and I cannot build and run the application again.

Description: Overlay display_EDT5.7_parallel_res_touch.dts does not work on Apalis iMX6 (activating the overlay does not show anything on the screen)

Description: Enable parallel RGB on Colibri iMX8X by default. Set resolution to 640x480.

Description: Enable U-Boot devicetree overlays support on Verdin modules

Description: Images running Balena do not support using docker-compose

Description: Fix bug that was preventing LVDS Atmel Tochscreen from working properly