[Bug 283892] Re: race condition with locking during update-manager dist-upgrade

[Maarten Bezemer]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version. When you test
it and it is still an issue, kindly upload the updated logs by running
apport-collect 283892 and any other logs that are relevant for this
particular issue.

** Changed in: update-manager (Ubuntu)
       Status: Triaged => Incomplete

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

Title:
  race condition with locking during update-manager dist-upgrade

Status in “update-manager” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: update-manager

  Hello! I've just noticed something weird:

  I have a machine with Ubuntu Hardy on it. Today I tried to upgrade to
  Intrepid, so I started 'update-manager -d'. It started doing its
  thing, everything seemed OK.

  In a separate terminal I was toying with aptitude, looking for a vnc
  package. I typed "aptitude install vnc-server"; I realized at the end
  that it couldn't work because of the update, but I pressed enter
  anyway to see what'd happen. Surprisingly, the update-manager coughed
  out an error. As far as I can tell, aptitude managed to take the
  "update lock" and start its thing, and the update-manager stumbled on
  it. (In fact, update-manager threw up the error, then continued
  installing a few things, and then stopped. I ran 'aptitude dist-
  upgrade' and it seems to continue correctly, but it's still going so
  I'm not sure everything will be A-OK.)

  I know this is not a common situation, but it still should be fixed.
  I'm not sure if the update-manager can take lock on behalf of whatever
  apps it's running, so perhaps it should detect lock failures and retry
  or ask the user what to do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/283892/+subscriptions