do-release-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)

[technologiclee]

After I installed everything in Synaptic Package Manager under the search result 'clam', there was an error to upgrading further packages. i tried running dpkg --configure -a . It failed with error 1.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.3
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CrashDB: ubuntu
Date: Mon Aug 4 16:40:10 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-annan-standard-precise-amd64-20130106-0
DuplicateSignature: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
ExecutablePath: /usr/bin/do-release-upgrade
InstallationDate: Installed on 2014-05-03 (93 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130106-02:29
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/do-partial-upgrade --frontend=DistUpgradeViewGtk3
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
PythonArgs: ['/usr/bin/do-release-upgrade', '--frontend=DistUpgradeViewGtk3']
SourcePackage: ubuntu-release-upgrader
Title: do-release-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
UpgradeStatus: Upgraded to trusty on 2014-06-05 (60 days ago)
UserGroups:

VarLogDistupgradeTermlog:

mtime.conffile..etc.update.manager.release.upgrades: 2014-06-04T23:14:57.606797

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1292996, so 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.