<div class="gmail_quote">Hello, Last few days I have been debugging a repaint issue in Weston. No repaint is triggered until an input event occurs or a Wayland client like simple-shm triggers one. Digging down, I see that struct weston_output.repaint is pointing to my output repaint function implementation. When I run weston and follow thru the logs, the repaint in my back-end implementation gets called when my 1. mouse moves/or an input event is sensed. 2. when a new client is launched. 3. when a client like simple-shm forces a repaint in a loop The intermittent screen repaints are timed long apart. So the screen doesn't get repainted until any one of the above event happens, which force a repaint. <a href="http://www.youtube.com/watch?v=VGZoFZ9MQX8&feature=youtu.be" target="_blank">http://www.youtube.com/watch?v=VGZoFZ9MQX8&feature=youtu.be</a> Here is a video of the behaviour. I launch simple-shm and then kill it (time 0:05), the screen isn't updated until I move my mouse (time 0:11). When I move the mouse the screen is updated and the residual simple-shm disappears from the screen, which is actually a repaint. Does any body else happen to see such behaviour ? Is there a way in wayland where in the frequency with which "weston_output_repaint for idle_repaint" is called, be increased ? Commits used <pre class="bz_comment_text" id="comment_text_0"> wayland: commit c855d6eec4c5e63489da5bc08451a2376e6d2aea weston : commit 5418a904ca007a109f6af8c0c75ca97a134986d9</pre> - </div>Regards, Abhijit Potnis