package linux-ubuntu-modules-2.6.24-16-generic 2.6.24-16.23 failed to install/upgrade:

[Charles Curley]

This may duplicate #222393. I got this running from update-manager (#225042), not synaptic.

I got this in the process of upgrading from Gutsy (as updated) to Hardy, and included updates since release. so I'm afraid I have no idea what happened nor what I expected (except a smoother upgrade).

root@taltos:~# lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04
root@taltos:~# find /var/cache/apt -iname linux*
/var/cache/apt/archives/linux-image-debug-generic_2.6.24.16.18_i386.deb
/var/cache/apt/archives/linux-image-debug-2.6.24-16-generic_2.6.24-16.30_i386.deb
root@taltos:~#

ProblemType: Package
Architecture: i386
Date: Wed Apr 30 20:45:20 2008
DistroRelease: Ubuntu 8.04
ErrorMessage:
 ErrorMessage: subprocess post-installation script returned error exit status 1
Package: linux-ubuntu-modules-2.6.24-16-generic 2.6.24-16.23
PackageArchitecture: i386
SourcePackage: linux-ubuntu-modules-2.6.24
Title: package linux-ubuntu-modules-2.6.24-16-generic 2.6.24-16.23 failed to install/upgrade:
Uname: Linux 2.6.22-14-generic i686

[Charles Curley (charlescurley)]

More information: when I ran "dpkg --configure -a", the initrd build stopped due to lack of space in /boot. I have kernel debug packages (/boot/vmlinux-debug-2.6.24-16-generic) installed. As that file occupied ~60 MB of a 100MB partition....

Workaround: I moved the vmlinux* package to /, reran the dpkg command. The initrd built successfully.

So a check on the available space in /boot might be a good idea.

Thanks

[Richard Birnie (rbirnie-deactivatedaccount)]

Thanks for reporting this bug. Could you please attach the log files from /var/log/dist-upgrade so we can try to find the cause of the problem. update-manager should already do a chack for free space in /boot so that makes this error curious. There are other bugs relating to failures of this calculation, hopefully the logs will help us figure out if this is one of those

[Charles Curley (charlescurley)]

tar/bzip2 ball attached per comment 3

After entering comment 2, I successfully rebooted & the computer is now running just fine.

[Jayson Rowe (jayson.rowe)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!