I'm not sure if anyone mentioned this yet, but it appears Mir's default
behaviour is to immediately draw a frame on compositor (re)start (for
non-nested servers only, like USC).
It's the last parameter here:
return std::make_shared<mc::MultiThreadedCompositor>(
the_display(),
the_scene(),
the_display_buffer_compositor_factory(),
the_compositor_report(),
!the_options()->is_set(options::host_socket_opt)); <=== bool
compose_on_start
I'm wondering if we've got that backwards. What we want to see on resume
is a new frame from the nested server propagate through. So that
statement should probably just be inverted:
the_options()->is_set(options::host_socket_opt));
Thus on resume, the first frame comes from the nested server. Although
we'd also want the same in the case of a single-server system.
--
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
