package linux-image-2.6.28-11-generic 2.6.28-11.41 failed to install/upgrade: Under Process post-installation script gave the error value 5 back

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance.

@Brian:
Here are the requested attachments. It was tricky to get the log files: Nautilus didn't display the file system except /home ("no permission", is this another bug or just some wrong settings?). I made it by an ordinary terminal (I'm a newbie!), couldn't get the admin terminal starting...

...this one tried to resist me, but I won.

The last one is empty ("term.log"), therefore it can't be uploaded.

The error that triggers the apport run is:

Richte linux-image-2.6.28-11-generic ein (2.6.28-11.41) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.28-11-generic
Failed to symbolic-link boot/initrd.img-2.6.28-11-generic to initrd.img.
dpkg: Fehler beim Bearbeiten von linux-image-2.6.28-11-generic (--configure):
 Unterprozess post-installation script gab den Fehlerwert 5 zurück

Hi Ralf,

Is this still an issue for you?

Hi Leann,

it isn't an issue for me anymore. Those things happened when I made an
upgrade to 9.04 beta. After some time I felt quite uncomfortable with
the situation, so I decided to make a complete new installation using a
final release image.

Hence, I didn't ever encounter that bug again.

Is there anything left I should do, e.g. close the threat or something
like that? (It was my first active community participation...)

Am Mittwoch, den 27.05.2009, 20:34 +0000 schrieb Leann Ogasawara:
> Hi Ralf,
>
> Is this still an issue for you?
>

The relevant (perl) code in the kernel postinst is:

    symlink($Old . "$link_name", $src_dir . "$link_name") ||
      die("Failed to symbolic-link " . $dest_dir . "$link_name to " . $src_dir
          . "$link_name .\n");
    warn "ln -s " . $Old . "$link_name " . $src_dir . "$link_name" if $DEBUG;

Unfortunately, it fails to include the error message ("$!"), so it would be very difficult to figure out what went wrong at this point.

Applies Matt's improved error reporting, though this is _not_ the solution to the original bug.

This bug was fixed in the package linux - 2.6.31-6.26

---------------
linux (2.6.31-6.26) karmic; urgency=low

  [ Andy Whitcroft ]

  * [Config] enable CONFIG_AUFS_BR_RAMFS
    - LP: #414738
  * split out debian directory ready for abstraction
  * add printdebian target to find branch target
  * abstracted debian -- debian/files is not abstracted
  * abstracted debian -- packages must be built in debian/<pkg>
  * abstracted debian -- kernel-wedge needs to work in debian/
  * abstracted debian -- ensure we install the copyright file
  * abstracted-debian -- drop the debian directories from headers
  * abstracted-debian -- drop the debian directories from headers part 2
  * SAUCE: ubuntu-insert-changes -- follow abstracted debian
  * [Upstream] aoe: ensure we initialise the request_queue correctly V2
    - LP: #410198

  [ Luke Yelavich ]

  * [Config] Ports: Disable CONFIG_CPU_FREQ_DEBUG on powerpc-smp
  * [Config] Ports: Re-enable windfarm modules on powerpc64-smp
    - LP: #413150
  * [Config] Ports: Build all cpu frequency scaling governors into ports
    kernels
  * [Config] Ports: Build ext2 and ext3 modules into ports kernels
  * [Config] Ports: CONFIG_PACKET=y for all ports kernels
  * [Config] Ports: Enable PS3 network driver

  [ Stefan Bader ]

  * abstracted debian -- call $(DEBIAN)/rules using make

  [ Tim Gardner ]

  * [Config] Abstract the debian directory
  * SAUCE: Improve error reporting in postinst
    - LP: #358564

 -- Tim Gardner <email address hidden> Sun, 16 Aug 2009 20:33:28 -0600