Comment 13 for bug 1654536

Was able to see the error on startup in the bug in USC.

Confirmed that the quirk affecting fb bits don't affect operation, and that both the overlay path and gl-rendered path work with the demo servers and USC (after the system has come up fully).

This only seems to happen when the device is booting up (haven't seen this on 'service lightdm restart') Just a hunch that there's something in the system at large that hasn't finished powered up correctly, when USC tries to GL-draw a frame.