[Bug 1284217] Re: [updates] Displays a spinner indefinitely when an update download was started externally

[Manuel de la Peña]

On Tue, Feb 25, 2014 at 4:39 PM, Barry Warsaw
<1284217 at bugs.launchpad.net>wrote:

> Okay, I think I see what you're getting at.  What you're observing is
> that when auto-downloads are enabled, you will get the UAS signal first,
> but the checking lock won't be released until after the download
> completes, at which time you'll also get a Update{Downloaded,Failed}
> signal.
>
> I did it this way because I still observed download failures when the
> checking lock was released during an automatic download.  Now, it's
> possible that the other fixes I and Manuel implemented would make those
> download failures go away (i.e. because of fixes to u-d-m, or
> workarounds in s-i), but we'd have to be very careful to test that
> vigorously before I'd be confident in releasing the check lock earlier.
>
>
Would be interesting to see what happens if you do not do that and if the
downloads occur they step on the present file... of course that means
reverting changes for testing, but if it fixes the issue...

Could an other solution tell the ui to connect to udm and check if there is
a download in process for the updates??? that way, before performing any
checkForUpdate we can ensure that the download is not being done. Am I just
saying something stupid?


I can think of a few other ways to handle this, short of mucking with
> the lock release:
>
> In the initial check that s-s performs, turn off automatic downloads.
> Then you'll get the UAS signal and lock release as quickly as possible.
> Then re-enable auto-downloads and issue the second CFU.  The actual
> check should return quite quickly, since we can use the cached results
> (we'll still have to grab the blacklist, but that shouldn't be much of a
> delay).
>
> Ah, I just thought of a possible middle ground: if CFU is called again
> after the actual checking phase is complete, but before the auto-
> download is complete, then we *do* have some available status and could
> send the UAS signal at that point.
>
> --
> You received this bug notification because you are a member of Ubuntu
> System Image team, which is subscribed to Ubuntu system image.
> https://bugs.launchpad.net/bugs/1284217
>
> Title:
>   [updates] Displays a spinner indefinitely when an update download was
>   started externally
>
> Status in Ubuntu system image (server/client/updater):
>   New
> Status in "system-image" package in Ubuntu:
>   New
> Status in "ubuntu-system-settings" package in Ubuntu:
>   Triaged
>
> Bug description:
>   These packages are currently in the CI train PPA
>   <https://launchpad.net/~ci-train-ppa-service/+archive/landing-010/>.
>   Upgrade to these first.
>
>   1. Make sure you're on auto download of updates (wi-fi) and that there's
> a system image update available to you
>   2. Open system-settings
>   3. Wait for "Updates available" to show, and click it
>   4. "Checking for updates" and an activity indicator appear
>   5. Wait. Don't let the screen blank (bug #1259326 - not sure this is
> actually still a problem but better safe than sorry). The update is
> downloading in the background at this point.
>   6.  When the update has finished downloading, you'll see the standard
> popover inviting you to install or cancel.
>
>   What should have happened is: instead of or shortly after step 4, we
>   should have seen the status of the in-progress download, just as if
>   we'd started it from the update panel.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-system-image/+bug/1284217/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1284217

Title:
  [updates] Displays a spinner indefinitely when an update download was
  started externally

Status in Ubuntu system image (server/client/updater):
  In Progress
Status in “system-image” package in Ubuntu:
  Triaged
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged

Bug description:
  These packages are currently in the CI train PPA
  <https://launchpad.net/~ci-train-ppa-service/+archive/landing-010/>.
  Upgrade to these first.

  1. Make sure you're on auto download of updates (wi-fi) and that there's a system image update available to you
  2. Open system-settings
  3. Wait for "Updates available" to show, and click it
  4. "Checking for updates" and an activity indicator appear
  5. Wait. Don't let the screen blank (bug #1259326 - not sure this is actually still a problem but better safe than sorry). The update is downloading in the background at this point.
  6.  When the update has finished downloading, you'll see the standard popover inviting you to install or cancel.

  What should have happened is: instead of or shortly after step 4, we
  should have seen the status of the in-progress download, just as if
  we'd started it from the update panel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1284217/+subscriptions