ubuntu-phone team mailing list archive

[Guillaume F <marsguo@xxxxxxxxxx>]

Hi Rodney and Michi,

Le 16/09/2015 23:04, Rodney Dawes a écrit :
> Hi Guillame,
>
> - Check in ~/.cache/upstart/scope-registry.log for network errors when
> accessing the store

Here are some errors when trying to use those scopes (I tried Ubuntu 
Store, 7Digital and Yahoo Finance)

   2015-09-17 14:28:30,012 - WARNING - WARNING: QApplication was not
   created in the main() thread.
   2015-09-17 14:29:10,116 - WARNING - QThreadStorage: Thread
   0xac212a88 exited after QThreadStorage 2 destroyed
   WARNING: QApplication was not created in the main() thread.
   Scope::preview() called.
   Scope::preview() called.
   Scope::preview() called.
   2015-09-17 14:30:17,598 - WARNING - QThreadStorage: Thread
   0xac280ba8 exited after QThreadStorage 2 destroyed

Actually, I managed to get the Ubuntu Store this time, after 2 or 3 
attempts. However, it's unusable, since the same problem appears if I 
navigate inside it.

> - Long press on an icon in Apps scope and see if store info loads there

Long press doesn't work, it keeps trying to load for approximately 1min 
and stops.

> - Try loading https://search.apps.ubuntu.com/api/v1/search?q= in browser

The page won't load on first try, half loads on second try (ie: I see a 
long text) but the loading bar never reaches completion even after 10 
tries. After a while, I get a network error (though other tabs are 
working fine).


Le 17/09/2015 01:33, Michi Henning a écrit :
> Hmmm... Are you saying that the remote scopes (such as Weather Channel) work if you are connected via WiFi, but don't work if you are connected via the cellular network?

Yes, exactly. I have no problem when connected via WiFi, but some scopes 
–all remote scopes I think– fail via the cellular network. Maybe it's 
just very very slow to load (sometimes I manage to get the store or a 
little bit of Amazon) but it's still unusable, since it will remain very 
very slow to load after each tap.

> If so, that suggests that the scopes runtime is almost certainly innocent. It has no idea how the phone is connected and just makes HTTP requests to the remote server. Failing only when connected via the cellular network would suggest some problem in the lower-level networking stuff, such as QNetworkAccessManager or below that.

Checking for updates in System Settings fails as well on cellular 
network, so that would confirm what you're saying.

In that case, should I still file a bug against unity-scope-click?

Then again, I could be a bit paranoid, but couldn't the operator be 
responsible for this selective slowdowns? I have the same problem with 
my self-hosted websites, and I discovered it with my previous (Android) 
phone. Question is, why would Free mobile block some websites, and what 
could I do about it?


Guillaume