do-release-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-release-upgrader (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
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-
ProcVersionSign
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
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
DuplicateSignature: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
ExecutablePath: /usr/bin/
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
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
LANGUAGE=en_US
PATH=(custom, no user)
PythonArgs: ['/usr/
SourcePackage: ubuntu-
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:
VarLogDistupgra
mtime.conffile.
| technologiclee (technologiclee) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| Changed in ubuntu-release-upgrader (Ubuntu): | |
| importance: | Undecided → Medium |
| information type: | Private → Public |
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.