update-manager crashed with ValueError in /usr/lib/python2.7/dist-packages/DistUpgrade/DistUpgradeController.py: bad marshal data (unknown type code)

[Michael Sinchenko]

123

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: update-manager 1:0.151.8
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
NonfreeKernelModules: wl
Architecture: i386
CurrentDmesg.txt:
 [ 35.600038] eth1: no IPv6 routers present
 [ 38.425296] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
Date: Mon Jul 4 20:39:08 2011
ExecutablePath: /usr/bin/update-manager
GConfNonDefault:
 /apps/update-manager/check_new_release_ignore=
 /apps/update-manager/first_run=false
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/update-manager --dist-upgrade
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager', '--dist-upgrade']
SourcePackage: update-manager
Title: update-manager crashed with ValueError in /usr/lib/python2.7/dist-packages/DistUpgrade/DistUpgradeController.py: bad marshal data (unknown type code)
UpgradeStatus: Upgraded to oneiric on 2011-06-27 (9 days ago)
UserGroups:

[RedSingularity (redsingularity)]

Since there is no private info in this report, I am marking it public.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[RedSingularity (redsingularity)]

Are you still getting this error with the latest updates?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Launchpad Janitor (janitor)]

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1058884, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.