There's a comment in unity-system-compositor (src/window_manager.cpp)
// We need to wait for the second frame before marking the session
// as ready. The first frame posted from sessions is a blank frame.
// TODO: Solve this issue at its root and remove this workaround
that led me to
On 28/05/15 17:35, Alan Griffiths wrote:
> There's a comment in unity-system-compositor (src/window_manager.cpp)
>
> // We need to wait for the second frame before marking the session
> // as ready. The first frame posted from sessions is a blank frame.
> // TODO: Solve this issue at it
"Since we don't post on startup we really ought to wait until we actually
have content from a client."
+1. Yes.
On Thu, May 28, 2015 at 11:35 AM, Alan Griffiths <
alan.griffi...@canonical.com> wrote:
> There's a comment in unity-system-compositor (src/window_manager.cpp)
>
> // We need to w
I've experienced this for a long time when running mir_proving_server
nested inside mir_demo_server_minimal. The screen doesn't go grey
(nested server is drawn) until a client is started in the nested server.
I feel it's a reasonable side-effect of us not drawing any "shell" in
demo servers. B
On Fri, May 29, 2015 at 2:35 AM, Alan Griffiths
wrote:
There's a comment in unity-system-compositor (src/window_manager.cpp)
// We need to wait for the second frame before marking the session
// as ready. The first frame posted from sessions is a blank
frame.
// TODO: Solve thi
Sorry for the confusion. Yes it's just a bug that needs fixing...
If one frame has been posted then you need to take it because you can
never predict how long before a second one arrives, if at all.
On 29/05/15 11:12, Christopher James Halse Rogers wrote:
On Fri, May 29, 2015 at 2:35 AM, A
