Ubuntu
unattended-upgrades package

unattended-upgrade crashed with CalledProcessError in check_output(): Command '['dpkg', '--force-confold', '--configure', '-a']' returned non-zero exit status 2

Bug #755090 reported by marcobra (Marco Braida) on 2011-04-08

This bug report is a duplicate of: Bug #754330: unattended-upgrade crashed with CalledProcessError in check_output(): Command '['dpkg', '--force-confold', '--configure', '-a']' returned non-zero exit status 2. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unattended-upgrades (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: unattended-upgrades

upgrading natty...

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unattended-upgrades 0.72ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sat Apr 9 00:30:57 2011
ExecutablePath: /usr/bin/unattended-upgrade
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade
ProcEnviron:
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/sh
PythonArgs: ['/usr/bin/unattended-upgrade']
SourcePackage: unattended-upgrades
Title: unattended-upgrade crashed with CalledProcessError in check_output(): Command '['dpkg', '--force-confold', '--configure', '-a']' returned non-zero exit status 2
UpgradeStatus: Upgraded to natty on 2011-04-08 (0 days ago)
UserGroups:

Tags:

Revision history for this message

marcobra (Marco Braida) (marcobra) wrote on 2011-04-08:

Traceback.txt Edit (469 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-04-08: This bug is a duplicate

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