[Touch-packages] [Bug 1340510] Re: [Mako] Session screen seen upon quick power key strike

2015-05-18 Thread Michael Terry
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) => (unassigned) -- 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: [Mako] Session screen seen u

[Touch-packages] [Bug 1340510] Re: [Mako] Session screen seen upon quick power key strike

2015-03-17 Thread kevin gunn
** Summary changed: - [Mako] Session screen seen upon quick power key strike only when roaming + [Mako] Session screen seen upon quick power key strike -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bu

[Touch-packages] [Bug 1340510] Re: [Mako] Session screen seen upon quick power key strike only when roaming

2015-03-17 Thread Alexandros Frantzis
> Krillin and Arale seem to behave fine, but I'm not sure if it's by accident - > do we actually have code that waits for something > (a new frame? feedback from shell?) before powering the screen on? Before turning the screen on/enabling the compositor, after the power button is pressed, USC cur

[Touch-packages] [Bug 1340510] Re: [Mako] Session screen seen upon quick power key strike only when roaming

2015-03-17 Thread Daniel van Vugt
No, the fix was proposed last year but never landed due to excessive delays outside of Mir that meant it couldn't help yet. See above branch. Might be worth revisiting and landing because if everything other than Mir is now behaving then we need it. -- You received this bug notification because y

[Touch-packages] [Bug 1340510] Re: [Mako] Session screen seen upon quick power key strike only when roaming

2015-03-17 Thread MichaƂ Sawicz
Hmm, I just tried on a freshly flashed mako with or without SIM (not roaming), and can reproduce this reliably. Krillin and Arale seem to behave fine, but I'm not sure if it's by accident - do we actually have code that waits for something (a new frame? feedback from shell?) before powering the sc