do-release-upgrade crashed with EOFError in /usr/lib/python3.2/email/utils.py: EOF read where not expected

[Timo Aaltonen]

installed quantal a month ago, ran apt-get dist-upgrade today (so no version upgrade, despite what I answered to apport) and got this halfway through

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: update-manager-core 1:0.164
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic x86_64
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
Date: Mon Jul 30 08:11:15 2012
ExecutablePath: /usr/bin/do-release-upgrade
GsettingsChanges:
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'launch-time' b'1340999649'
 b'com.ubuntu.update-manager' b'window-height' b'500'
 b'com.ubuntu.update-manager' b'window-width' b'600'
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/lib/update-manager/check-new-release -q
PythonArgs: ['/usr/lib/update-manager/check-new-release', '-q']
SourcePackage: update-manager
Title: do-release-upgrade crashed with EOFError in /usr/lib/python3.2/email/utils.py: EOF read where not expected
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Brian Murray (brian-murray)]

Is this recreatable using the command line information in the bug description? I don't think it will be because this report is about a rather old version of update-manager 164 vs 168 or so and check-new-release was moved to the ubuntu-release-upgrader package.

[Launchpad Janitor (janitor)]

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

[pererik87 (pererik87)]

I have the same bug on a fresa install of 12.10. How to reproduce. insert ubuntu cd and install -> boot -> and the bug is there

[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.