Ubuntu
update-manager 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 #304928 reported by alekos on 2008-12-03

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
	update-manager (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: update-manager

Description: Ubuntu 8.10
Release: 8.10

$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.93.34
  Candidate: 1:0.93.34
  Version table:
*** 1:0.93.34 0
        500 http://us.archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     1:0.93.32 0
        500 http://us.archive.ubuntu.com intrepid/main Packages

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

NonfreeKernelModules: fglrx
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-19-generic i686

Tags:

Revision history for this message

alekos (alekos) wrote on 2008-12-03:

Dependencies.txt Edit (4.1 KiB, text/plain; charset="utf-8")
VarLogDistupgradeAptlog.gz Edit (13.9 KiB, application/x-gzip)
VarLogDistupgradeApttermlog.gz Edit (105.2 KiB, application/x-gzip)
VarLogDistupgradeMainlog.gz Edit (11.0 KiB, application/x-gzip)
VarLogDistupgradeTermlog.gz Edit (63.8 KiB, application/x-gzip)

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-12-04:

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.