Comment 15 for bug 1255045

Cool. Sounds like a simple problem then, of Mir just failing to schedule a compositor frame on wakeup.

Normally frames are scheduled only when a surface changes. When no surface is changing, no frames are scheduled, resulting in better power management. So the touch is what triggers some surface to change, and then a frame gets scheduled.

Obviously we need to force a frame to be scheduled when the screen wakes up, as a special case. If we're not doing it already... (?)