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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637841 Title: Today scope refresh not always working on MX4 with OTA 13 To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
