** Changed in: unity-scopes-shell (Ubuntu)
Status: Confirmed => In Progress
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Description changed:
The trusted prompt for location access for Scopes is shown immediately
after the wizard and not after first search or pull-to-refresh initiated
by the user as intended. For some reason it happens only if wizard is
involved in the boot sequence, and not if trusted prompt for location is
just forced by removing .scopesLocationPrompt and trust store db.
Looking at the unity8-dash.log file from the first boot after wiping the
device, it seems that there is a forced refresh of scopes registry
metadata early during the dash startup:
[2016-04-23:07:04:42.593] Refreshing scope metadata
[2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope
with id 'com.canonical.scopes.weatherchannel'"
[2016-04-23:07:04:42.983] Dispatching search:
"com.canonical.scopes.dashboard_dashboard" "" ""
[2016-04-23:07:04:42.987] Enabling location updates
This calls invalidateResults() and has the same effect as pull-to-
refresh.
+
+ This is most likely caused by the network becoming available & remote
+ scopes getting fetched for the first time, signaling new scopes get
+ available to the shell.
+
+ To reproduce, reflash with --wipe or perform factory reset.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1595421
Title:
Location trusted prompt shown immediately after the wizard
Status in Canonical System Image:
New
Status in unity-scopes-shell package in Ubuntu:
In Progress
Bug description:
The trusted prompt for location access for Scopes is shown immediately
after the wizard and not after first search or pull-to-refresh
initiated by the user as intended. For some reason it happens only if
wizard is involved in the boot sequence, and not if trusted prompt for
location is just forced by removing .scopesLocationPrompt and trust
store db.
Looking at the unity8-dash.log file from the first boot after wiping
the device, it seems that there is a forced refresh of scopes registry
metadata early during the dash startup:
[2016-04-23:07:04:42.593] Refreshing scope metadata
[2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope
with id 'com.canonical.scopes.weatherchannel'"
[2016-04-23:07:04:42.983] Dispatching search:
"com.canonical.scopes.dashboard_dashboard" "" ""
[2016-04-23:07:04:42.987] Enabling location updates
This calls invalidateResults() and has the same effect as pull-to-
refresh.
This is most likely caused by the network becoming available & remote
scopes getting fetched for the first time, signaling new scopes get
available to the shell.
To reproduce, reflash with --wipe or perform factory reset.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421/+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
