Weston.ini is empty sometimes

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello Erik,

Thank you for reaching out with your question. It sounds like you’re encountering an unusual issue where the weston.ini file in your weston-vivante container occasionally becomes empty, causing a locking screen on your Verdin iMX8MP device. Let’s explore some potential causes and solutions:

1. Container Restart Behavior: If the container restarts, it might not properly reinitialize the weston.ini file. Ensure your Docker Compose setup is configured to persist this file across restarts.

2. Volume Binding: Double-check your volume bindings in the Docker Compose file. Make sure the weston.ini file is correctly mounted and that the source path on the host contains the desired configuration. Incorrect bindings could lead to the file being overwritten or not found.

3. Startup Scripts: Review any startup scripts within the container that might overwrite the weston.ini file. It’s possible that an entry script or initialization process is modifying this file.

4. File Permissions: Verify that the file permissions allow the container to read and write to the weston.ini file as needed. Incorrect permissions might prevent proper access or modification.

5. Docker Compose Configuration: Ensure your Docker Compose file is correctly set up, particularly the volumes section, to bind the weston.ini file from the host to the container.

To further troubleshoot, you might want to manually inspect the weston.ini file on the host to ensure it contains the correct configuration before starting the container. Additionally, monitor the container logs for any errors or warnings related to the weston.ini file during startup.

By ensuring the correct setup and monitoring the container’s behavior, you should be able to identify and resolve the issue with the weston.ini file becoming empty. If the problem persists, consider testing with a minimal setup to isolate the cause.

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

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

VNC Access not working with Portainer Weston-vivante container

Hi, Just getting started with Torizon and having some issues getting VNC and RDP to work. I’ve started my Weston container using the command in this tutorial Remote Access the TorizonCore GUI Using VNC or RDP | Toradex Developer Center and I can see it running in Portainer. However, when trying to connect with either RDP or TightVNC, I’m getting the following error: TightVNC: “No connection could be made because the target machine actively refused it” A “ps -e” run on the host doesn’t show an…

Weston.ini rotate not working

Prob a simple one, but I previously used the following in the weston.ini to rotate the screen 90 degrees. [output] name=HDMI-A-1 transform=rotate-90 If I change HDMI-A-1 to HDMI-A-2 it complains so at least I know my ini file is being loaded. It’s not rotating the screen. Is there a different syntax for Torizon OS 6.7

Screen Capture Issue on Wayland Application Running with Weston Compositor on iMX7D SoM.