inconsistent disappearance of child scope on Today scope

Hi,

Thanks for reporting this!

Can you test this:
* In Holidays child scope Settings, ensure location data is enabled
* In Today scope Settings, disable all child scopes except Holidays and ensure location is enabled
* Refresh Today many many times.

You should *always* see holidays scope with holidays data. If you do not see holidays data, can you please attach this file to this bug:
/home/phablet/.cache/upstart/scope-registry.log

Note: By design, when location data is disabled, the Holidays child scope does not provide data and so it does not display in the Today scope (although it does display a message saying location data is needed when viewing the Holidays child scope itself). This seems sensible because holiday data is fundamentally based on the user's location. If we displayed (cached) holidays data when the user had location data off, it could be incorrect for example if the user traveled.

I enabled location detection using wifi + GPS and restarted the phone, verified that location detection is turned on in both Today and Holiday scopes, disabled all child scopes in Today scope except Holidays and the child scope appeared there like 1 in 5 reloads only (at best).

I also noted that while reloading the Holiday scope itself (not Today scope), the scope sometimes asks to enable location data even when it is always turned on.

Thanks for testing that.

Very interesting that Holidays scope shows the message "Location data must be enabled" even when you location data turned on.

This could either be a bug in the holidays scope (it has location data but it does not think it does), or perhaps the location data passed to the holidays scope by the framework is not correct.

To code that checks whether there is location data is very simply and is here:
http://bazaar.launchpad.net/~holidays-scope-team/holidays/trunk/view/head:/src/query.cpp#L207

If there is no location data, the message it displayed and the scope ends.

This does not look buggy to me, so I suspect the scope is not being passed correct location data by the framework. So I am going to add unity-scope-api task to this bug.

Added unity-scopes-shell because scopes-api just passes through what it gets from the shell.

Status changed to 'Confirmed' because the bug affects multiple users.