package linux-image-2.6.28-15-generic 2.6.28-15.52 failed to install/upgrade: subprocess post-installation script returned error exit status 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
The linux kernel package fails to install correctly. Complete log below.
Note: I have uninstalled grub and replaced it with lilo. Grub (at least grub1; I have not tried grub2) doesn't work on my HW (hard reboot before even displaying the grub menu). Hence, it is no surprise that the hook scripts can't find the update-grub script/binary. The kernel package should still support lilo, since lilo is packaged.
root@severn:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up linux-image-
Running depmod.
update-initramfs: Generating /boot/initrd.
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)
Could not find postinst hook script [update-grub].
Looked in: '/bin', '/sbin', '/usr/bin', '/usr/sbin'
dpkg: error processing linux-image-
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
linux-
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 2
HibernationDevice: RESUME=
MachineType: VIA Technologies, Inc. VT8367-8233/5
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
SourcePackage: linux
Title: package linux-image-
Note: After the above, I installed the grub package (but hopefully did not install grub to the MBR/PBR), and the post-install steps triggered by grub appear to have resolved this issue. Still, that's a workaround; I shouldn't need grub installed if I don't use it.