Let me rephrase that...
The problem seems to be that MultiThreadedCompositor (unity-system-compositor)
unconditionally recomposes on restart:
compose_on_start = true;
This means the user is guaranteed to see an old frame on restart because
we've allowed no time for clients (included nested servers) to provide
any new frames.
We should probably just sleep for a second or so in
MultiThreadedCompositor on restart. That will allow clients time to
provide a new frame (as soon as they can). And then only if no clients
have provided a new frame after that delay should
MultiThreadedCompositor force a recompose itself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1340510
Title:
session screen seen upon quick power key strike
Status in Mir:
In Progress
Status in Mir 0.4 series:
Won't Fix
Status in Mir 0.5 series:
Won't Fix
Status in Unity System Compositor:
New
Status in The Unity 8 shell:
New
Status in “mir” package in Ubuntu:
Confirmed
Status in “unity8” package in Ubuntu:
Confirmed
Bug description:
Image #125 on N4
1) boot phone and unlock phone to display dash
2) strike power key to blank & unblank screen quickly
3) the dash is seen instead of lockscreen for a brief moment
logging against u-s-c as this was fixed, but power policy changes may
have effected this
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1340510/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
