[Touch-packages] [Bug 1540056] Re: App scope does not auto-populate after boot

2016-03-01 Thread Pat McGowan
*** This bug is a duplicate of bug 1545866 ***
https://bugs.launchpad.net/bugs/1545866

** This bug has been marked a duplicate of bug 1545866
   First scope results only load after unlock

-- 
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/1540056

Title:
  App scope does not auto-populate after boot

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540056/+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


[Touch-packages] [Bug 1540056] Re: App scope does not auto-populate after boot

2016-02-11 Thread Alejandro J. Cura
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => backlog

-- 
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/1540056

Title:
  App scope does not auto-populate after boot

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540056/+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


[Touch-packages] [Bug 1540056] Re: App scope does not auto-populate after boot

2016-02-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity-scopes-shell (Ubuntu)
   Status: New => Confirmed

-- 
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/1540056

Title:
  App scope does not auto-populate after boot

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540056/+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


[Touch-packages] [Bug 1540056] Re: App scope does not auto-populate after boot

2016-02-03 Thread Pat McGowan
Agreed its not an ideal user experience
This is not new with this update fwiw


** Also affects: unity-scopes-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => Wishlist

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

-- 
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/1540056

Title:
  App scope does not auto-populate after boot

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540056/+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