Comment 5 for bug 1597717

This 0x0 buffer problem was uncovered because rev3539 changed the order in which nested::Display and nested::HostConnection and the CursorController are created. In 0.23 the Display was created later so there would not be any MirSurfaces for the nested::DisplayBuffer, on which the CursorController would submit its initial default cursor image (via the HostConnection interface). So the initial setup was always lost. I "fixed" that by storing the cursor image inside the HostConnection impl and also changed the order of things.

And as it turns out in one path we do check for the size of the cursor image.. and in the other we do not..