App scope does not auto-populate after boot
Bug #1540056 reported by
Guillaume F
This bug report is a duplicate of:
Bug #1545866: First scope results only load after unlock.
Edit
Remove
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Confirmed
|
Wishlist
|
Alejandro J. Cura | ||
| unity-scopes-shell (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
When you boot your phone, no matter how long you wait after you first started it, you have to first unlock it before the app scope populates. It's not very good from a user experience point of view, since you start with a blank screen. This scope should auto-populate on start (and maybe others too, but then there's the problem of data connexion).
I think the problem was not present before OTA9.
Tested on the Aquaris 4.5 updated to OTA9.
Revision history for this message
| Pat McGowan (pat-mcgowan) wrote | #1 |
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → Alejandro J. Cura (alecu) |
| importance: | Undecided → Wishlist |
| milestone: | none → ww08-2016 |
| status: | New → Confirmed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in unity-scopes-shell (Ubuntu): | |
| status: | New → Confirmed |
| Changed in canonical-devices-system-image: | |
| milestone: | ww08-2016 → backlog |
To post a comment you must log in.
Agreed its not an ideal user experience
This is not new with this update fwiw