package linux-ubuntu-modules-2.6.24-2-generic None failed to install/upgrade: subprocess post-removal script returned error exit status 1

[Cantastorie]

Upgrading from Gutsy to Heron alpha 2

ProblemType: Package
Architecture: i386
Date: Sun Dec 30 23:04:05 2007
Dependencies:

DistroRelease: Ubuntu 8.04
ErrorMessage: subprocess post-removal script returned error exit status 1
Package: linux-ubuntu-modules-2.6.24-2-generic None
PackageArchitecture: i386
SourcePackage: linux-ubuntu-modules-2.6.24
Title: package linux-ubuntu-modules-2.6.24-2-generic None failed to install/upgrade: subprocess post-removal script returned error exit status 1
Uname: Linux Godot 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux

[Nicolas DERIVE (kalon33)]

Hello all,

Using Hardy, I've the same problem when trying to delete and purge linux-ubuntu-modules-2.6.24-4-generic after installing the 2.6.25-generic one with the new kernel.

[Joel C. Salomon (jcsalomon)]

Work-around: when uninstalling a kernel-module package, do a complete uninstall (purge) right away; the regular uninstall leaves not enough in the system for the purge to work.

[Leann Ogasawara (leannogasawara)]

Hi Cantastorie,

I'm reassigning this to the update-manager package. It is responsible for upgrading packages within a release, and upgrading a release of Ubuntu to the next one. If this is still an issue, can you please take a look at https://wiki.ubuntu.com/DebuggingUpdateManager and provide the requested information under the "Debugging Procedures" section. Thanks!

[Leann Ogasawara (leannogasawara)]

Hi Cantastorie,

My mistake, this was correctly filed against the kernel and has been updated accordingly. However, we are still curious if this is an issue for you? Please let us know. Thanks!

[Cantastorie (fusaroli)]

It was still an issue two days ago, when I did a clean re-install of ubuntu gutsy (I'll be travelling for a while and need absolute stability ;) ).

[Leann Ogasawara (leannogasawara)]

Thanks for testing and the feedback. Please note that if you are requiring stability, "Pre-releases of Hardy are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage." So running Gutsy as you have decided to do seems to be the right approach. When you get a chance and are able to reattempt the upgrade from Gutsy to Hardy, could you attach the updated error messages and log files for when you attempt the upgrade from Gutsy to Hardy that would be great. Also, just for future reference if you could attach your files unzipped that would be appreciated as well. Thanks.

[Daniel Hahler (blueyed)]

I'm marking this as duplicate of bug 149836.