Every time I walk away from my computer, while running weston, long enough for a screensaver to kick in, when I come back it's hung. My monotor's light indicating that it's getting no video input. alt-sysreq-reisub does reboot.
SardemFF7 says this is caused by the lock screen which comes up when it receives input after running the screensaver, and was apparently discussed by krh and pq.
The weston.ini man page seems to say that an empty screensaver section will disable the screensaver. But I guess that just means no application is display, the screen is still blanked and locked?
Is there some kind of workaround to get the lock screen to not happen?
alt-sysrq-r, ctrl-alt-del does work from this state.
Launching weston with a -i0 command line argument (as mentioned in the weston man page) does sound like an effective workaround.
The command line for the above workaround is:
weston-launch -- -i0
And it does appear to work for me.
Darxus, how would you like to proceed with this bug? Nobody else has indicated that this is problem. Is this still a problem for you?
Just a note that this happened to me just now, running weston 1.2, wayland
head, radeon r600.
I think we found this problem, try this commit from master:
Author: Kristian Høgsberg <firstname.lastname@example.org>
Date: Wed Oct 16 11:10:12 2013 -0700
compositor: Stop the repaint loop if the compositor went to sleep
We check the state when we schedule a repaint, but we will still repaint
in weston_output_finish_frame() if a repaint is needed. Now we check
whether we went to sleep while waiting for the page flip and stop repainting
in that case.