update-manager crashed with CacheExceptionDpkgInterrupted in __init__()

[mikeyphi]

Binary package hint: update-manager

Following an update, received the following message at the end of the install process

sudo dpkg --configure -a
Setting up initramfs-tools (0.92bubuntu64) ...
update-initramfs: deferring update (trigger activated)

Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-12-generic
cpio: ./lib/udev/firmware.sh: Function stat failed: No such file or directory
update-initramfs: failed for /boot/initrd.img-2.6.32-12-generic
dpkg: subprocess installed post-installation script returned error exit status 1

ProblemType: Crash
Architecture: i386
Date: Wed Feb 10 16:08:22 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091224)
InterpreterPath: /usr/bin/python2.6
Package: update-manager 1:0.131.4
PackageArchitecture: all
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager --dist-upgrade
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
PythonArgs: ['/usr/bin/update-manager', '--dist-upgrade']
SourcePackage: update-manager
Title: update-manager crashed with CacheExceptionDpkgInterrupted in __init__()
Uname: Linux 2.6.32-12-generic i686
UserGroups:

[mikeyphi (mikeyphi)]

There have been many instances of this error which is (apparently) solved by editing firmware.sh and deleting the .sh term.

[mikeyphi (mikeyphi)]

This bug seems to be a repeat of 519946

[Apport retracing service (apport)]

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 #519882, 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.