On 22/01/14 19:16, Pat McGowan wrote:
> I tried to get the debug output by adding the env var to the unity8.conf for upstart
> I deleted the existing unity-scope-click log file but it was never recreated after I set up the test.
>
> This is easy to reproduce by setting nameserver 10.0.0.0 in
> /etc/resolv.conf and rebooting.
>
> The symptom is when you first expand the installed apps you see only the
> first 9. After around 10-20 secs the rest of the apps appear, then 10
> secs later it goes back to just 9, etc.
>
This may be a similar symptom as seen on the emulator; nothing from the
click scope is shown until you perform a search.
My original bug comment was to not tie the apps available on the store
to the apps installed to avoid the network dependency (success or fail)
which introduces a wait of comparable timing when compared to the legacy
apps.
On 22/01/14 19:16, Pat McGowan wrote:
> I tried to get the debug output by adding the env var to the unity8.conf for upstart
> I deleted the existing unity-scope-click log file but it was never recreated after I set up the test.
>
> This is easy to reproduce by setting nameserver 10.0.0.0 in
> /etc/resolv.conf and rebooting.
>
> The symptom is when you first expand the installed apps you see only the
> first 9. After around 10-20 secs the rest of the apps appear, then 10
> secs later it goes back to just 9, etc.
>
This may be a similar symptom as seen on the emulator; nothing from the
click scope is shown until you perform a search.
My original bug comment was to not tie the apps available on the store
to the apps installed to avoid the network dependency (success or fail)
which introduces a wait of comparable timing when compared to the legacy
apps.