package udev 162-2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Johannes Skartland]

Binary package hint: udev

Tried to open a FAT32 USB stick connected to the pc.

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: udev 162-2.1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Wed Dec 29 13:27:49 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: System Manufacter System Product Name
ProcCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
SourcePackage: udev
Title: package udev 162-2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
dmi.bios.date: 01/11/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: IP35-E (Intel P35+ICH9/R)
dmi.board.vendor: http://www.abit.com.tw/
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: System Enclosure Manufacter
dmi.chassis.version: OEM
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/11/2008:svnSystemManufacter:pnSystemProductName:pvrSystemVersion:rvnhttp//www.abit.com.tw/:rnIP35-E(IntelP35+ICH9/R):rvr1.0:cvnSystemEnclosureManufacter:ct3:cvrOEM:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System Manufacter

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, the package installation error message that you have received is actually a failure with lzma and a generic one at that. The following steps may help resolve the issue. Please execute the following command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again as this may resolve your issue. We plan to make lzma errors more informative and that work is being tracked in bug 691985 which I will mark this a duplicate of.