Looking into this in more detail, there seems to be some issues with the
scopes that the dashboard scope aggregates:


1. If I have no favourited contacts on my phone, when the scope gets to pushing 
favourite contact results it just seems to close and stop pushing any further 
results (no results from other aggregated scopes are returned thereafter).


2. Upcoming events seems to get stuck in the query run() method (loading bar 
moves back and forth for a while), then after some time the events scope 
crashes:

"RegistryObject::ScopeProcess: Scope:
"com.canonical.scopes.events_events" closed unexpectedly. Either the
process crashed or was killed forcefully."


3. Without a FitBit account (Note: adding a FitBit account via settings doesn't 
even work for me), the FitBit scope gets stuck in the scope's start() method, 
then after 4s the scopes runtime gives up and logs a timeout:

"2014/10/07 06:35:50 Starting fitbit scope
ScopeBase::run(): unity::scopes::TimeoutException: Request timed out after 5000 
milliseconds"


So, the best I can do is favourite a contact, then disable both "Display 
upcoming events" and "Display your FitBit stats", then the scope works just 
fine. In fact, the scope works this way even without the changes in the linked 
branch.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376054

Title:
  Scope Registry fails when aggregating an aggregator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1376054/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to