Qt5-wayland-vivante tagging version issue

Technical Support
,
1

I’m testing a Qt application with QML. The main idea is to display a second window from the same application.

Problem:
When trying to display the second window, both freeze (there are no problems loading the QML file).

Sample code:

#include <QGuiApplication>
#include <QQmlApplicationEngine>

int main(int argc, char *argv[]) {
QGuiApplication app(argc, argv);
QQmlApplicationEngine engine;

engine.load(QUrl(QStringLiteral("qrc:/window1.qml")));

engine.load(QUrl(QStringLiteral("qrc:/window2.qml")));

return app.exec();
}

  • My application is dockerized with Weston and the application. I’m using the weston-vivante:2 image to run the composer.

  • I’ve tried QQuickWindow and QQuickWidget with the same result.

  • I found the solution by changing the application’s base image from qt5-wayland-vivante:2.6 to qt5-wayland-vivante:3 but I’d like to know why it didn’t work.

Q1: Where can I find information about the differences in the image tags (qt5-wayland-vivante:2.6 vs. qt5-wayland-vivante:3) to understand why it works in 3 version?

I’ve compared the image layers in the Torizon Docker Hub repository, but I can’t find anything relevant

qt5-wayland-vivante:3

qt5-wayland-vivante:2.6

Q2: Should I compare another information to know the reasons?

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!

Regarding your first question, the Debian containers for Torizon do not use the ‘latest’ tag to ensure compatibility between specific container images and Torizon OS versions. This approach helps maintain stability and predictability in your development environment.

To understand the differences between container versions, you can:

  1. Consult the Torizon OS Containers Tags and Versioning Documentation: This resource provides detailed information on compatibility and versioning.

  2. Review Hardware Acceleration Support: Qt5 containers with Wayland offer hardware acceleration, which can enhance performance.

  3. Examine the Weston Compositor Configuration: This is crucial as it manages window operations for Wayland applications.

The differences you observe might be due to enhancements in hardware acceleration or Wayland compositor integration across versions.

For more detailed information, you might find these resources helpful:

I hope this helps! If you have any more questions, feel free to ask.

Best regards,
Toradex AI Assistant

3

Greetings @agustinc,

Where can I find information about the differences in the image tags (qt5-wayland-vivante:2.6 vs. qt5-wayland-vivante:3) to understand why it works in 3 version?

The container image tag number denotes, what version of Torizon OS this was meant to be used for.

  • Tag of 2.X means it was made for Torzion 5.X
  • Tag of 3.X means it was made for Torizon 6.X
  • Tag of 4.X means it was made for Torizon 7.X

I’m not sure what version of Torizon you are using on your device. But I imagine it wasn’t compatible with the 2.6, which is why you saw issues. We have to do this versioning because the versions of GPU drivers and such change on the OS side. To be compatible the containers must be updated alongside the OS.

Best Regards,
Jeremias

4

Thanks for the reply.

I’m using this device:
-apalis-imx8-06804694
-TorizonCore 5.7.0+build.17 (dunfell)
-Kernel: Linux 5.4.193-5.7.0+git.f78299297185
-Architecture: arm64

Based on your answer, I should be using 2.X tags. I tried qt5-wayland-vivante:2.8.2, the latest 2.X tag, and that didn’t work either, but thanks anyway.

5

TorizonCore 5.7.0+build.17 (dunfell)

Is there a reason you are using the 5.7.0 version? The reason I ask, is because this is a rather old version of Torizon and is considered end-of-life with no active support today.

Based on your answer, I should be using 2.X tags. I tried qt5-wayland-vivante:2.8.2, the latest 2.X tag, and that didn’t work either, but thanks anyway.

It could be that your use-case here only works on the newer versions of Qt/Weston/Wayland. The 2.X tags of course use older versions of everything which is possibly a factor here.

Best Regards,
Jeremias

1 Like