Skip to main content
Use this procedure to restore Weston after a DRM mode test or restart Weston during display troubleshooting. If Weston is already active and the display works, return to the procedure that brought you here.
Connect to the target through SSH and run target commands from the root shell. For instructions, see Sign in using SSH.
If you followed Run DRM modetest, Weston was already stopped. Press Ctrl+C in the terminal running modetest to end the test, then go directly to step 2. Follow the recovery steps only if Weston fails to start.

1. Stop Weston if it is running

Stop Weston and its socket so a client connection cannot start it again during cleanup:
It is safe to run this command when both units are already stopped.

2. Start Weston

Start the socket and Weston service:

3. Verify that Weston is running

Check the service state:
The expected result is active. Confirm that Weston appears on the connected display, then return to your original procedure.
Continue with steps 4–7 only if startup fails or the service is not active. If the service is active but the display remains blank, return to the troubleshooting page for your display interface.

4. Check for remaining Weston processes

Stop the socket and service before checking for a remaining Weston process:
Look for any remaining Weston compositor processes:
This lists each matching process ID (PID) and its command line.
If there is no output, no Weston compositor process remains. Skip step 5 and continue to step 6.

5. Stop any remaining Weston processes

If step 4 lists a remaining Weston process, replace <PID> with its numeric PID and run:
If more than one Weston process is listed, repeat the command for each PID. Check again to confirm that they have exited:
Continue when there is no output.

6. Retry startup

Clear the failed state and any startup rate limit from previous attempts:
Start the socket and service again:
Check the service state:
If the result is active and Weston appears on the display, return to your original procedure. If startup still fails, continue to step 7.

7. Inspect the startup errors

Inspect the socket and service status:
Check the recent logs:
Use the reported error to investigate the startup failure. If the service is active but the display remains blank, return to the troubleshooting page for your display interface.