Hi Kyle and Michi,
Just to let you know, I still have the problem with the Today scope
refresh / messed up icons, on my MX4 with OTA-14 installed. I was
wondering if you had any time to look again at this problem.
Merry Christmas and happy new year to you all!
Best regards
Dave H
--
You
Hi Michi,
OK thanks for checking and I agree with your explanation as you can see
similar problems with other scopes. I guess the Today scope looks worse
(and more annoying) as its the main scope you see each time the phone is
active, others are not always checked or used. Also the scopes with
The connectivity status is something that is *not* set by scopes-api.
Instead, the status is received by scopes-api from whoever makes the
query (typically, the shell) and then passed through to the scope. In
turn, the shell just passes on what it gets from QNetworkAccessManager,
I believe.
We
Hi Kyle,
Thanks for the Test scope. I installed it and found a similar result to
you. If you keep repeating the refresh every 30s (ten times in my case)
you get a mixed result.
1. 1 unknown / 2 unknown
2. 1 unknown / 2 unknown
3. 1 connected / 2 unknown (after pull refresh in Today scope and
Dave - thanks.
My guess is this has nothing to do with the Today scope.
I guess is that there is something in the plumbing that does not handle
losing a network during a fresh - so I am glad that Michi is aware.
Regarding network, I wrote and attached here a test scope that displays
the scopes
** Description changed:
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1637841
Title:
Today scope refresh not always working on MX4 with OTA 13
Status in Today
Hi Kyle,
Thanks for all your efforts to try to resolve this issue. I have install
the file you sent using the below method:
Logged onto my MX4 in developer mode using adb shell (in read only
mode). Copied your file to the phone Download directory and:
phablet@ubuntu-phablet:~/Downloads$ pkcon
Thanks for all the detective work!
I suspect that the MiddlewareException in coincidental and caused by an
earlier timeout. But we shouldn't get stuck like this and things should
recover transparently if the network goes away. I'll have a look and see
what's going on.
--
You received this bug
Given my above experiences, and given that you do have elpais installed
and it may be enabled in your Today scope (can't see from your settings
image in comment #7), can you please:
Ensure that El Pais and holidays scopes are DISABLED in today scope
settings, and see if you can reproduce this?
twice now with elpais and holidays disabled in Today during refresh I
walked out of wifi range and *expected* resulted displayed [1]. Display
was not limited to Day scope.
Possibility: these child scopes do not handle loss of network during
refresh correctly. They should simply return from the
ok, with holiday scope disabled, I walk out of wifi range while a today scope
refresh is ongoing and I get similar results:
* only the Day scope displays
* but this time a different child scope displays the TimeoutExecption: elpais
[2016-11-03 17:12:03.323] ERROR:
by the way, issuing "restart scope-registry" brings holidays scope back
to life and fixes the today scope on refresh.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
Noting the TimeoutException on holidays scope above, I've tried
launching holidays from Manage page. No results display.
running holidays scope from command line with scope-data tool I get this with
no displayed results:
phablet@ubuntu-phablet:~$ ./scope-data
After walking back into wifi range (on my second reproduction) and
refreshing Today scope, only Day scope displays (although it does
display normally).
The scope-reg.log contains this now reliably on refresh with only Day scope
showing:
[2016-11-03 16:56:46.984] INFO: Registry:
I was just able to produce a MiddelwareException twice by walking out of
range of my wifi while a Today scope refresh was in progress.
In both case the resulting display ONLY the Day scope.
In one case there was also a twitter scope panic/crash.
Attached my scope-reg.log
** Attachment added:
David H,
Assuming you have not modified any other parts of your rootfs, let's get
you the latest Today scope and see if you can reproduce any of the
issues, just to be sure.
Please install the attached and reboot (just to get the logs cleared)
and comment back with further info.
** Attachment
David H.
In one of your other bugs about Today scope display issues [1], I think
you mentioned that you made the rootfs "/" read-write (in order to
change the default scope background as I recall).
Doing this is inherently dangerous and can cause all kinds of problems
that are essentially
And provide the scope-registry.log if the issue is reproduceable with
that recent today scope. (I am interested to see if the
MiddlewareExecption occurs again).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api
Hi David H.
So, a few things which I will address in separate comments for clarity.
First, your scope-registry.log contains a
unity::scopes::MiddlewareException
[2016-11-02 17:04:35.351] ERROR:
com.canonical.scopes.dashboard_dashboard: ReplyImpl::error():
unity::scopes::MiddlewareException:
19 matches
Mail list logo
