package linux-image-2.6.32-22-generic 2.6.32-22.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 10

[Nuty]

Binary package hint: linux-headers-2.6.32-22-generic

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 2.6.32-22-generic /boot/vmlinuz-2.6.32-22-generic
run-parts: executing /etc/kernel/postinst.d/nvidia-common 2.6.32-22-generic /boot/vmlinuz-2.6.32-22-generic
run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 10
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.32-22-generic.postinst line 1003.

...

Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 2.6.32-22-generic /boot/vmlinuz-2.6.32-22-generic
run-parts: executing /etc/kernel/header_postinst.d/nvidia-common 2.6.32-22-generic /boot/vmlinuz-2.6.32-22-generic
run-parts: /etc/kernel/header_postinst.d/nvidia-common exited with return code 10
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-2.6.32-22-generic.postinst line 110.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Fri Jun 4 15:30:56 2010
ErrorMessage: run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 10
SourcePackage: nvidia-common
Title: package linux-image-2.6.32-22-generic 2.6.32-22.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 10

[Brian Murray (brian-murray)]

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 514840, 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. Please continue to report any other bugs you may find.