Problems with out of the box Hello World app in .NET UNO platform

Hi everyone.
I followed the documentation to setup my system in order to execute the sample app in .NET UNO Platform. The application starts successfully, as I am able to hit breakpoints at early stages of application startup. Problem is, when the GUI has to be displayed, the system hangs with the message:

“Windows.UI.Composition.CompositionObject[0]
The member void CompositionObject.Dispose() is not implemented in Uno.
Uno.UI.RemoteControl.RemoteControlClient[0]
Failed to connect to the server (timeout).”

I’m trying to run this on a Colibri iMX6DL/S, Iris v2.0A carrier board.
Can you give any hint on where to look for this problem?
The application executes correctly when run on Skia UNO Platform on the development machine (Windows 10 64 bit), but fails when Torizon is set as the target device

Update: after further investigation, I notice it’s the complete Torizon UI that freezes during application startup. This means, no more mouse control on cursor. Anyway, the system is still alive, since I am able to connect via SSH.

Dear @Lorenzo,

Can you please share with us a few more details on your configuration?

  • Which exact Colibri iMX6 and version are you using?
  • Which version of TorizonCore do you have running on the module?
  • Which extension are you running and which version?
  • When you say that the system freezes, can you get any log from journalctl?

Best regards,

Hi, I finally managed to run the application in TorizonCore.
By executing “docker stop $(docker ps -q)” the display unfreezes and the application is displayed.
I don’t think it’s the correct solution, though…

  • Colibri iMX6DL 512MB v1.1Y
  • Iris V2.0A
  • TorizonCore Upstream 5.6.0+build.13 (dunfell)
  • Toradex Torizon Support v1.4.0

Dear @Lorenzo, thanks for the feedback.

I’m glad you could run it. Sometimes what may happen is that your Weston container was already open and it was used by another application. Sometimes, it may not allow you to start a new one. Depending on how you run the containers from the extension, it will not kill/stop previous running containers.

Please come back if you start having problems again.

Best regards,