Search by Tags

Torizon OS Issue Tracker


The following table contains known issues, scheduled bug fixes, and feature improvements for the Torizon OS images. The tickets are split into two major states:

  • Submitted (open): new features and bug fixes for Torizon OS versions that have not yet been released. They may be scheduled for a specific release version; not planned; or in our backlog. All of them have one of the following states:
    • Known Issue: a bug or unexpected behavior that has been reported and pending a fix. Once fixed, the status will transition to Fixed.
    • Feature Request: a new feature that may be added to a future release. Once released, the status will transition to New Feature.
  • Released (closed): new features and bug fixes for BSP versions that have already been released. All of them have one of the following states:
    • Fixed: a bug that has been fixed and released.
    • New Feature: something that didn't exist before and was added to a news release.

Any schedules are not guaranteed but reflect the current planning. The planning could be shifted due to priority changes.
Issues that are scheduled for a specific version will be integrated into the mentioned version of the BSP.

We will update this table continuously in order to always provide the latest state of our development plan.

Please see also the Toradex Embedded Linux Support Strategy to learn more about the different releases.

How to obtain the Torizon OS Images

Using the Toradex Easy Installer application in a Toradex SoM connected to the internet is the easiest and fastest way to install the latest version of Torizon OS into the device. Toradex also offers offline installers.

Clear Filter
Issue #StatusSubjectModuleComponentsSeverity

6.2.0-devel-202303 (Release date: 2023-03-07)
6.2.0-devel-202303 monthly pre-release
TOR-2761FixedAktualizr is rebooting mid-process during synchronous updates with big container imagesNot applicableAktualizrLow

Description: When synchronous updates happen, the reboot command may be called before the container (application) updates are finished, leading to a reboot in the middle of the process. This leads to an update failure and rollback to the previous state. This was seen with big containers when performing offline updates. Although it has never been reported, in theory, this bug can affect online updates as well.

Workaround: A workaround for TorizonCore 5.7.y and 6.1.0 is available. A side-effect of the workaround is that updates take longer to complete.
Create a new configuration file for Aktualizr as specified in the article Aktualizr - Modifying the Settings of Torizon Update Client, with the following contents:
[uptane] force_install_completion = true
Then, disable the current reboot mechanism as specified in the section enabling and disabling automatic reboot.
This configuration will still trigger the reboot, and it's expected to take a longer time before it happens.