Ubuntu
vdr package

package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)

Bug #315787 reported by Robin Mallinson on 2009-01-10

This bug report is a duplicate of: Bug #238755: 'Account has expired' message when adding a new user, after "passwd -l root". Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	vdr (Ubuntu)	Triaged	Undecided	Unassigned

Bug Description

Binary package hint: update-manager

This was an auto generated bug report while upgrading from 8.04 to 8.10 this morning (10thJan09)

ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 8.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)

Package: update-manager 1:0.93.34
PackageArchitecture: all
SourcePackage: update-manager
Title: package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
Uname: Linux 2.6.24-22-generic x86_64

Tags:

Revision history for this message

Robin Mallinson (rmallins) wrote on 2009-01-10:

Dependencies.txt Edit (4.1 KiB, text/plain; charset="utf-8")
VarLogDistupgradeAptautoinstfixuplog.gz Edit (417 bytes, application/x-gzip)
VarLogDistupgradeAptlog.gz Edit (38.9 KiB, application/x-gzip)
VarLogDistupgradeApttermlog.gz Edit (141.1 KiB, application/x-gzip)
VarLogDistupgradeMainlog.gz Edit (14.8 KiB, application/x-gzip)
VarLogDistupgradeMainprereqlog.gz Edit (500 bytes, application/x-gzip)
VarLogDistupgradeTermlog.gz Edit (83.0 KiB, application/x-gzip)

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2009-01-10:

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 238755, 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. Feel free to continue to report any other bugs you may find.