net connection should refresh scopes

Bug #1229241 reported by Dave Morley on 2013-09-23
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libunity
Triaged
Medium
Unassigned
libunity (Ubuntu)
Medium
Unassigned
unity8 (Ubuntu)
Medium
Unassigned

Bug Description

Currently when you start the phone from a fresh flash you get the first time use guide. This blocks networks from initialising. Because of this there might not be a connection when the system first boots. This means that click apps and network based scopes and their options aren't available.

Unity should refresh the Scopes once a network connection is confirmed.

Michał Sawicz (saviq) on 2013-09-23
Changed in unity8:
status: New → Triaged
importance: Undecided → Medium
milestone: none → ubuntu-13.10
Omer Akram (om26er) on 2013-09-23
tags: added: avengers qa-touch
Changed in libunity:
importance: Undecided → Medium
Dave Morley (davmor2) on 2013-09-23
tags: removed: qa-touch
tags: added: qa-touch
Changed in libunity:
status: New → Confirmed
Michal Hruby (mhr3) on 2013-10-16
Changed in libunity:
status: Confirmed → Triaged
tags: added: scopes-s
Michał Sawicz (saviq) on 2014-09-03
Changed in unity8 (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Michał Sawicz (saviq) on 2014-09-09
no longer affects: unity8
HuangZhiquan (huangzhiquan) wrote :

i use networkinfo for help,get the current networkmode,and then get the accesspointname,when you connect to net and success, dashcontent will refresh all scopes

Paweł Stołowski (stolowski) wrote :

The attached fix for unity8 looks good and will most likely do what it's supposed to do, but I wonder if this is good strategy. What this change effectively means is: if scope is currently active (visible) while network becomes available, it will be refreshed; if it's not visible (but favorited), it will be marked "dirty" and refreshed when user swipes/selects it. To my understanding this will affect not only the after-boot scenario, but normal usage as well. What if network is flaky and goes offline/online a lot? We'll end up re-querying scopes more often than necessary, disregarding TTL of the results (currently visible results may still be "valid", but forcefully refreshed just because network gets available). Perhaps the shell should cooperate more closely with shell plugin with this, rather than forcing refresh?

HuangZhiquan (huangzhiquan) wrote :

Yes, thanks,maybe what i deal with it seems rude(dash will refresh only when device connect successfully). We don't always want to refresh some scopes when net connect. But i don't know when we need to refresh scopes or when we leave scopes alone, flaky network is also a question for this bug. (refreshing with a blank scope is a question needs to deal)

Albert Astals Cid (aacid) wrote :

Honestly i think this should be done on the unity-scopes-plugin rather than on the unity-dash itself, the unity-scopes-plugin has more information about whether a network reconnect should end up in a refresh or not.

Changed in libunity (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers