On Tue, Feb 4, 2014 at 4:50 AM, Alexander Sack <[email protected]> wrote:
> On Fri, Jan 31, 2014 at 7:55 PM, Michał Sawicz > <[email protected]> wrote: > > On 31.01.2014 18:37, Łukasz 'sil2100' Zemczak wrote: > >> > >> I have tried looking > >> into one of the unity8 crashes on install-and-boot tests, but it seems > >> the crash file is corrupt. > > > > > > Please whenever you see a unity8 crash, make sure to look inside > unity8.log: > >> > >> what(): could not activate surface with eglMakeCurrent > > > > > > That's a known issue raising from the fact display wasn't ready when > unity8 > > was trying to start. And then it gets respawned by upstart straight away > and > > starts working. So does not affect test results in any way. > > How can we ensure that display is ready before trying to start? > The requirement from Mir is that the system is powered on before starting the display server process. If its acceptable for these tests, you can run 'powerd-cli active' before the test run. We still haven't worked out a nicer solution than this architecturally. Thanks, Kevin
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
