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: RegistryObject::ScopeProcess::exec(): Process for scope: "com.canonical.scopes.dashboard_dashboard" started "com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: com.canonical.scopes.day_day, local_id: day_localId" "com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: com.canonical.scopes.weatherchannel, local_id: weather_channel_localId" "com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: com.canonical.scopes.holidays_holidays, local_id: holidays_localID" "com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: com.canonical.scopes.events_events, local_id: events_localID" "com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: com.canonical.scopes.tasks_sctasks, local_id: tasks_localID" "com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: com.canonical.scopes.contacts_contacts, local_id: contacts" "com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: com.canonical.scopes.fitbit_fitbit, local_id: fitbit_localId" "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: com.canonical.scopes.calls_calls, by keyword recent, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: com.canonical.scopes.texts_texts, by keyword recent, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: com.ubuntu.telegram_sctelegram, by keyword recent, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: com.canonical.elpais_ELPAIS, by keyword news.headlines, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: com.canonical.scopes.bbc_bbc, by keyword news.headlines, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: com.canonical.scopes.eljueves_eljueves, by keyword news.headlines, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: com.canonical.scopes.euronews_euronews, by keyword news.headlines, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: com.canonical.scopes.testscope_testscope, by keyword news.headlines, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: knitzsche.testscope-art_testscope-art, by keyword news.headlines, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: knitzsche.testscope-emblem_testscope-emblem, by keyword news.headlines, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: knitzsche.testscope-mascot_testscope-mascot, by keyword news.headlines, to department: " "com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: twitter.canonicalpartners_twitter, by keyword twitter.home, to department: " "com.canonical.scopes.dashboard_dashboard: NOT using departments" aa_getcon failed, errno = 13 [2016-11-03 16:56:50.987] INFO: Registry: RegistryObject::ScopeProcess::exec(): Process for scope: "com.canonical.scopes.day_day" started QSocketNotifier: Can only be used with threads started with QThread QSocketNotifier: Can only be used with threads started with QThread QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.1084" (uid=32011 pid=1344 comm="/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperun") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1710 comm="NetworkManager ")" QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.1084" (uid=32011 pid=1344 comm="/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperun") interface="org.freedesktop.NetworkManager" member="GetDevices" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1710 comm="NetworkManager ")" "Object path cannot be empty" query complete, status: ok [2016-11-03 16:56:51.548] ERROR: com.canonical.scopes.dashboard_dashboard: QueryBase::run(): unity::scopes::TimeoutException: Request timed out after 500 milliseconds (endpoint = ipc:///run/user/32011/zmq/priv/com.canonical.scopes.holidays_holidays, op = debug_mode) [2016-11-03 16:56:51.924] INFO: Registry: RegistryObject::ScopeProcess::on_process_death(): Process for scope: "com.canonical.scopes.dashboard_dashboard" exited [2016-11-03 16:56:51.925] ERROR: Registry: RegistryObject::ScopeProcess: Scope: "com.canonical.scopes.dashboard_dashboard" closed unexpectedly. Either the process crashed or was killed forcefully. [2016-11-03 16:57:31.224] INFO: Registry: RegistryObject::ScopeProcess::on_process_death(): Process for scope: "com.canonical.scopes.day_day" exited -- 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 Scope: Incomplete Status in unity-scopes-api package in Ubuntu: New Bug description: Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak or no wifi the today scope is messed up, in the same way as the below report I found for the BQE4.5. If you try to refresh it the problem is not resolved (such as only half the date shown, or no date or no pictures). Even after returning to a good wifi signal and performing the pulldown refresh the problem is not resolved. As I have seen this problem from the start on older OTA versions (I have reported before), my feeling is there is a fundamental problem with the way scopes are refreshed when you pull down the screen. I have also screen the "no pictures" on other scopes and the refresh not working, could this be a common scope problem and nothing to do with the today scope?. Note, when the today scope is messed up if you un-tick the "day info" then refresh and then tick day info again, this sometimes helps. If no pictures displayed (today and other scopes) I normally have to reset the phone to correct the problem. Your support us appreciated, Regards Dave H Similar bug (BQE4.5 & OTA9) * Upon updating today screen (swipe-down) get partially updated info, see attached step01.png * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes were updated, but they somehow ended up above today screen controls, see attached step02.png * Activating side bar again makes it look like on attached step03.png * Finally, pressing on Ubuntu icon once more results in empty today screen, step04.png To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
