What happend to the gstreamer libraries on the toradex.source repository ?!

Technical Support
, ,
1

After 3 days thinking our code had altered itself somehow, we finally figured out that our debug code was throwing an exception due to updated gstreamer libs in the toradex repositories. We’ve solved the issue by using the following in our dockerfiles

RUN mkdir -p /home/toradex &&
mv /etc/apt/sources.list.d/toradex.sources /home/toradex/

RUN apt-get update
&& apt-get install -y --no-install-recommends
libqt6multimedia6:arm64
alsa-utils:arm64
gstreamer1.0-plugins-base:arm64
gstreamer1.0-plugins-good:arm64
gstreamer1.0-alsa:arm64

#RUN mv /home/torizon/toradex.sources /etc/apt/sources.list.d/

(that last line fails to work - I don’t know why - some more pain from using containers that I really don’t need).

The fix means that the dependent libs for libqt6multimedia6 that are loaded come from the debian repository - version 1.22, rather than the 1.24 version found on the toradex repository.

Obviously this is a quick fix so that I can get on with some of the work I really need to be doing - no doubt the toradex repository will be fixed in the near future - and possibly another test case added for Qt audio services…

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I’d be glad to help troubleshoot this GStreamer library issue! To provide the most accurate guidance, could you let me know:

  1. Which OS and version are you running? (e.g., Torizon OS 6.x.x, Torizon OS 7.x.x)
  2. Which hardware are you using? (e.g., Verdin iMX8M Plus, Apalis iMX8, Colibri iMX8X)
  3. Which base container image are you building from? (e.g., torizon/wayland-base-vivante:3, torizon/debian:3)

You can get detailed information about your system by running the tdx-info command on your device. More details are available at https://developer.toradex.com/software/development-resources/tdx-info/(1)

General Guidance on GStreamer and Toradex Repositories

Based on the documentation, when working with GStreamer on Torizon OS containers:

Toradex Debian Feed Configuration

The Toradex Debian containers are configured with the Toradex package repository feed, which provides hardware-accelerated packages(1). The repository configuration is set up as follows in the base containers:

echo "Types: deb\n\
URIs: https://feeds1.toradex.com/debian/snapshots/$TORADEX_SNAPSHOT\n\
Suites: testing\n\
Components: main non-free\n\
Signed-By: /usr/share/keyrings/toradex-debian-repo.gpg" > /etc/apt/sources.list.d/toradex.sources \
 && echo "Package: *\nPin: origin feeds1.toradex.com\nPin-Priority: 900" > /etc/apt/preferences.d/toradex-feeds

(1)

This configuration gives Toradex packages priority (pin-priority 900) over standard Debian packages(1).

Installing GStreamer Packages

For proper GStreamer installation on different hardware platforms, the documentation provides specific package lists. For example, on iMX8-based SoMs:

RUN apt update
RUN apt install -y libgstreamer1.0-0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly gstreamer1.0-libav gstreamer1.0-doc gstreamer1.0-tools gstreamer1.0-x gstreamer1.0-alsa gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-qt5 gstreamer1.0-pulseaudio

(2)

Recommended Approach

Rather than disabling the Toradex repository, the recommended approach is to:

  1. Use the appropriate Toradex base container image for your hardware and Torizon OS version(1)
  2. Ensure compatibility between your Torizon OS version and container image tags(1)
  3. Install the required GStreamer packages as documented for your specific platform(2)

Once you provide the specific details about your setup (OS version, hardware, and base image), I can give you more targeted guidance on resolving the library compatibility issue you’re experiencing.

Best regards,
Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Actually the solution is already in my initial post…

4

You’re absolutely right—my apologies! I understand you’ve already found a workaround by temporarily disabling the Toradex repository to use Debian’s GStreamer 1.22 packages instead of the 1.24 version from the Toradex feed.

Your solution of moving /etc/apt/sources.list.d/toradex.sources before installing the packages effectively prevents the Toradex repository from being used during package installation, forcing apt to pull from the standard Debian repositories instead.

Regarding the last line that fails to work (moving toradex.sources back), the path discrepancy might be the issue—you’re moving from /home/toradex/ but trying to restore from /home/torizon/. Try this correction:

RUN mv /home/toradex/toradex.sources /etc/apt/sources.list.d/

This should restore the Toradex repository configuration after your package installation completes.

Your observation about the version mismatch between GStreamer 1.24 (Toradex repository) and 1.22 (Debian) causing issues with Qt6 multimedia dependencies is valuable feedback for the Toradex team to investigate compatibility with Qt audio services.

Best regards,
Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

5

Good job spotting the typo - if the VSCode container based build actually showed me the original error from the bash command, I might have spotted it myself - but hey, what’s a little more suffering.

valuable feedback for the Toradex team

Does the AI automatically advise the team ?

6

Greetings @Timo,

I reported this issue you brought here to our team. This change in our package feed was not fully intended. The team has been doing some work related to Gstreamer recently, and this work made it’s way into our toradex.sources package feed before being fully ready. Our team will work to amend this behavior in package feed.

Thank you bringing this to our attention, and apologies for the inconvenience this caused.

Best Regards,
Jeremias

1 Like