package linux-image-2.6.28-15-generic 2.6.28-15.48 failed to install/upgrade: subprocess pre-installation script returned error exit status 1

Bug #416008 reported by Jeenu V
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Error encountered while upgrading via. apt-get

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess pre-installation script returned error exit status 1
HibernationDevice: RESUME=UUID=29ba19eb-c9ce-4548-9801-7b6b066bda30
MachineType: Dell Inc. MM061
Package: linux-image-2.6.28-15-generic 2.6.28-15.48
ProcCmdLine: root=UUID=55e3a787-1620-4311-a5fe-14dc6237dfb6 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.28-15.48-generic
SourcePackage: linux
Title: package linux-image-2.6.28-15-generic 2.6.28-15.48 failed to install/upgrade: subprocess pre-installation script returned error exit status 1

Revision history for this message
Jeenu V (jeenuv) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I notice the following in your DpkgTemrinalLog. Did you have something else running in the background which would have been blocking? Maybe try again. Thanks.

debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

dpkg: error processing /var/cache/apt/archives/linux-image-2.6.28-15-generic_2.6.28-15.49_i386.deb (--unpack):

 subprocess pre-installation script returned error exit status 1

Changed in linux (Ubuntu):
status: New → Invalid
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

See bug 271246 for more info if interested.

Revision history for this message
Jeenu V (jeenuv) wrote :

From what I noticed from bug 271246, the problem disappeared after reboot, which is not the case with me; this occurs consistently even after reboot. Running fuser on the config.dat file didn't return anything either. Any other logs that I should look into?

Changed in linux (Ubuntu):
status: Invalid → New
Revision history for this message
Rob! C (rpchristina) wrote :

Getting the following when attempting to execute 'sudo dpkg --configure -a'

Setting up linux-image-2.6.28-15-generic (2.6.28-15.52) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.28-15-generic
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.28-15.49 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.28-15.49 was configured last, according to dpkg)
Running postinst hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.28-15-generic
Found kernel: /boot/vmlinuz-2.6.28-11-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... /usr/sbin/update-grub: line 1516: /boot/grub/menu.lst: Operation not supported
User postinst hook script [/sbin/update-grub] exited with value 1
dpkg: error processing linux-image-2.6.28-15-generic (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-2.6.28-15-generic

Revision history for this message
Jeenu V (jeenuv) wrote :

I worked around the error by removing (read backup) nvida-common script from two locations under /etc/; "find /etc -maxdpeth 2 -name nvdia-common" should list those two. I'm unaware of "other" implications of this method, but from what I know, all my package related issues disappeared with this. But I believe this is a bug nevertheless, and has to be addressed properly.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

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 349469, 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.

Changed in linux (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.