This is not a bug in unity-scopes-api. The problem was that unity8-dash
has become an app recently, and qtmir sends SIGSTOP five seconds after
the greeter appears. Suspending the dash at random unpredictable times
is a big no-no because the signal can strike while a request-reply
interaction with a scope is in flight, causing the RPC to time out when
the dash is eventually resumed. It can also happen that the signal
arrives while results are trickling in from a scope, causing either no
results at all to appear or, alternatively, truncating the results at
some random point.
After installing qtmir packages I got from Ted that do not suspend the
dash, things work perfectly fine.
I also checked CPU consumption of the dash and, while the dash isn't
doing any work, it is completely quiescent. The CPU consumption problem
that was observed earlier was almost certainly related to bug #1364464
and bug #1374206, both of which are fixed.
I think qtmir should change the policy and exclude unity8-dash from the
list of apps that are suspended. We are the authors of unity8-dash and,
if the dash bleeds CPU cycles, we should fix the dash rather than
plastering over the problem by suspending the dash.
Right now, the dash is fine and does not use CPU when idle.
** Changed in: unity-scopes-shell (Ubuntu)
Status: Incomplete => Invalid
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1382039
Title:
[TOPBLOCKER] Apps scope empty on boot
Status in “qtmir” package in Ubuntu:
Confirmed
Status in “unity-scope-click” package in Ubuntu:
Invalid
Status in “unity-scopes-api” package in Ubuntu:
Invalid
Status in “unity-scopes-shell” package in Ubuntu:
Invalid
Status in “unity8” package in Ubuntu:
Invalid
Bug description:
Several people reported today that the apps scope came up empty on
boot. A pull-to-refresh makes results come in again.
Note: it seems the problem is more likely to happen if you wait for at
least 1 minute after reboot, and then unlock your device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382039/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
