[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-20 Thread Pat McGowan
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked To

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-15 Thread Michał Sawicz
** Changed in: qtubuntu (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked To manage

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-08 Thread Jean-Baptiste Lallement
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked To

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-06 Thread Launchpad Bug Tracker
** Branch linked: lp:~dandrader/qtmir/dontOccludeFreshSurfaces -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked To manage notifications about

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-06 Thread Paweł Stołowski
Yep, the attached MP fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked To manage notifications about this bug go to:

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-06 Thread Michał Sawicz
** Changed in: canonical-devices-system-image Status: Confirmed => In Progress ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: qtubuntu (Ubuntu) Status: New => In Progress ** Changed in: qtubuntu (Ubuntu)

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-06 Thread Launchpad Bug Tracker
** Branch linked: lp:~saviq/qtubuntu/revert-occlude-lp1620297 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked To manage notifications about

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-05 Thread Paweł Stołowski
** Description changed: The pre-populating of first scope on startup (before the screen is unlocked) doesn't seem to be fully working. My early investigation shows that the shell plugin correctly pre- populates scope model on startup when the screen is still locked, but after

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-05 Thread Michał Sawicz
I'm afraid the fix to bug #1475678 caused this... Dash isn't told to render until the screen is unlocked. Wonder if we should only tell apps to not render after a few seconds... Or make the dash an exception... ** Package changed: unity8 (Ubuntu) => qtubuntu (Ubuntu) ** Changed in:

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-05 Thread Paweł Stołowski
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked To

[Bug 1620297] Re: First scope not rendered until unlocked

2016-09-05 Thread Paweł Stołowski
Attaching a snippet of unity8-dash.log. Apps scope is my 1st scope. Note, how it's pre-populated @15:03:44 on startup and delivers 29 results: [2016-09-05:15:03:44.547] Pre-populating first scope: "clickscope" I waited ~2 minutes before unlocking the device - this is when I think rendering