package nvidia-kernel-common 20051028+1+nmu2ubuntu2 failed to install/upgrade: files list file for package `dcraw' contains empty filename

[Ramesh]

Binary package hint: nvidia-kernel-common

Hi everybody, this is ramesh from india.
i am relatively new to ubuntu. just 5months old.
i had probs with my screen resolution locking at 800x600. i m using a samsung LCD monitor. there is no graphic card. i use NVIDIA 610i motherboard. i have upgraded from Hardy to Intrepid Ibex using the alternate CD. soon after that i am unable to set the resolution. i even tried to activate the NVIDIA hardware drivers but it is hanging up. finally i tried to update through update manager, but it gave the error,
E: Could not get lock /var/cache/apt/archives/lock - open (11 Resource temporarily unavailable)
i deleted the files lockfile-remove, lockfile-create,lockfile-touch from location /usr/bin
even then the update problem did not get rectified.
finally i tried from terminal by typing: $ sudo aptitude safe-upgrade
The screenshot of this is shown.
please check it solve my problem.
i dont have resolution as well as no updates..

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: files list file for package `dcraw' contains empty filename
Package: nvidia-kernel-common 20051028+1+nmu2ubuntu2
PackageArchitecture: all
SourcePackage: nvidia-kernel-common
Title: package nvidia-kernel-common 20051028+1+nmu2ubuntu2 failed to install/upgrade: files list file for package `dcraw' contains empty filename
Uname: Linux 2.6.27-9-generic i686

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

The error is
 files list file for package `dcraw' contains empty filename

This particular bug has already been reported and is a duplicate of bug 108189, 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.