update-manager crash on update from 9.10 to lucid

[Chris Irwin]

Binary package hint: update-manager

While running `update-manager -d`, X crashed and restarted in displaying an error about running in failsafe-mode. Unfortunately it appears to have hung the machine.

I ran recovery console and had it configure the remaining packages.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: update-manager 1:0.133.11
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
Date: Wed Apr 7 10:43:31 2010
EcryptfsInUse: Yes
PackageArchitecture: all
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager

[Chris Irwin (chrisirwin)]

<cirwin> I was attempting an upgrade using `update-manager -d`, but it
seems that X failed while configuring packages, then froze while
trying to restart gdm (probably due to unconfigured packages). Is
there any way to resume the update-manager process?
<mvo> cirwin: if the machine is still running, the upgrader is in
/tmp, you can run it from there again
<yofel> kwtm: the beta2 images should be available as torrents when
they are released tomorrow
<mvo> cirwin: it does support text mode
<mvo> cirwin: could you please file a bug with all the logs attached?
<mvo> cirwin: logs in /var/log/dist-upgrade/* ?
<yofel> kwtm: but you can just get a daily image (http or zsync) today
though, there won't change much
<cirwin> mvo it is not still running.
<cirwin> mvo, I could do it with dpkg, I just knew that update-manager
does more foo than that. Didn't want to miss out.
<mvo> cirwin: it does do a bit more, like removing obsolete packages
and auto-removable ones, but if you are fluent with synpatic/apt/dpkg
you can just do that yourself e.g. with the synaptic obsoeletes and
auto-removable status in synaptic
<mvo> cirwin: but please send the logs so that the failure can be analyized
<cirwin> mvo, will do. `ubuntu-bug update-manager`?
<mvo> cirwin: that should work

[Michael Vogt (mvo)]

Thanks for the logs, unfortunately they don't give me a clue, do you have anything in /var/crash that looks like it was created at around the time of the crash?

[Jean-Baptiste Lallement (jibel)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".
Thanks again!