This should be taken care of outside of Mir. Currently the issue occurs due to the unity-system-compositor stopping the compositor before the shell/greeter has a change to show any shutdown animation.
On display power off: powerd sends D-Bus signal setScreenPowerMode("off") to com.canonical.Unity.Screen unity-system-compositor receives signal, stops mir compositor and turns off screen powerd emits DisplayPowerStateChange signal unity8 shell receives DisplayPowerStateChange - attempts to show greeter rendering is blocked since USC stopped compositor. There may some frames queued up with content before greeter animation hence the issue reported here. On display power on: powerd sends D-Bus signal setScreenPowerMode("on") to com.canonical.Unity.Screen unity-system-compositor receives signal, starts compositor and turns on screen mir compositor starts, unity8 shell rendering continues from where it left off. For now a workaround is to add a configurable delay at power off in unity-system-compositor: https://code.launchpad.net/~albaguirre/unity-system-compositor/add-power-off-delay-option/+merge/208281 The ideal solution is better coordination between powerd, the shell/greeter and USC; The shell should be given an opportunity to show a shutdown animation. Maybe Mir could add a parameter to the compositor stop to specify how many frames to render before actually stopping though I don't see this as necessary. Perhaps the shell should be in charge of notifying USC when to power off instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1233564 Title: Wrong frame is seen on wake up/resume/unlock. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1233564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs