Vino-server Autostarting but Stopping Automatically on Orin Nano

Issue Overview

Users are experiencing issues with the vino-server on the Nvidia Jetson Orin Nano, where the server autostarts during system boot but subsequently stops automatically. The symptoms include:

• Service Status: When checking the service status using systemctl --user status vino-server.service, it shows as "inactive (dead)" shortly after booting.
• Error Logs: The logs indicate that the process is killed with a signal of TERM, suggesting an abnormal termination.
• Environment: The issue occurs on Jetpack 5.1.1 running Ubuntu 20.04, transitioning from a previous setup on Xavier NX without problems.
• Frequency: This issue consistently arises during system startup but can be manually restarted without issues once the system is up.
• User Experience Impact: Users are unable to utilize VNC features immediately after boot, leading to a less efficient workflow.

Possible Causes

The potential causes for this issue may include:

• Configuration Errors: The service file for vino-server may not be correctly configured for the Orin Nano environment.
• Software Bugs: There could be bugs in Jetpack 5.1.1 that affect service management during startup.
• Driver Issues: Compatibility issues between the vino-server and the Orin Nano’s drivers could lead to unexpected behavior.
• Environmental Factors: Running the device in hotspot mode may interfere with the normal operation of vino-server, as some users reported similar issues when using this configuration.
• User Errors: Misconfigurations during setup or incorrect service management commands could contribute to the problem.

Troubleshooting Steps, Solutions & Fixes

Here are detailed troubleshooting steps and potential solutions:

1. Check Service Configuration:

   • Verify that the vino-server.service file is correctly configured. It should look like this:

     [Unit]
     Description=Vino VNC server
     
     [Service]
     Type=dbus
     BusName=org.gnome.Vino
     ExecStart=/usr/lib/vino/vino-server
     Restart=on-abnormal
     

2. Manual Start Test:

   • After booting, run:

     systemctl --user restart vino-server.service
     

   • If this works, it confirms that the service can run manually but fails to start automatically.

3. Add Delay in Service Start:

   • Modify the service file to include a delay before starting:

     ExecStartPre=/bin/sleep 10
     

   • Note that users reported issues with this approach, indicating it may not resolve the problem.

4. Adjust Startup Method:

   • As a workaround, remove the systemd service link from /usr/lib/systemd/user/graphical-session.target.wants and add /usr/lib/vino/vino-server to Ubuntu’s Startup Applications.

5. Enable Screen Sharing:

   • Ensure that screen sharing is enabled through Settings -> Sharing -> Screen Sharing. This is crucial for vino-server to function properly.

6. Run in Hotspot Mode:

   • If running as a Wi-Fi hotspot, try disabling this feature temporarily to see if it resolves the issue.

7. Use Direct Command Execution:

   • As a last resort, users can execute vino-server directly using:

     DISPLAY=:0 /usr/lib/vino/vino-server &
     

8. Update Jetpack Version:

   • Consider updating to Jetpack 5.1.2 if feasible, as newer versions may contain fixes for known issues.

9. Check System Logs:

   • Monitor logs for any additional error messages that could provide insight into why the service fails at startup:

     journalctl --user -u vino-server.service
     

10. Community Feedback:

    • Engage with community forums or NVIDIA support for additional insights or similar experiences from other users.

By following these steps, users should be able to diagnose and potentially resolve the issue with vino-server on their Nvidia Jetson Orin Nano.