Linux package setup failed during upgrade when "3 way merge" selected for menu.lst

[sedatk]

I chose "3 way merge" for menu.lst conflicts and package setup failed right after.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage:
 ErrorMessage: subprocess post-installation script returned error exit status 3
HibernationDevice: RESUME=UUID=60cda159-37c6-42ed-a667-3eefedb4ffbc
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gateway Gateway M320 and 4500 Series
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=034ff835-2bc2-45d8-83f1-e2c738ec0fee ro quiet splash
ProcVersionSignature: Ubuntu 2.6.27-11.27-generic
SourcePackage: linux
Title: package linux-image-2.6.28-11-generic 2.6.28-11.42 failed to install/upgrade:

[Niels Holmgaard (niels-holmgard)]

The setup process fails to merge the new kernel as a menu item for grub when menu.lst has been edited manually. It is not difficult to fix manually afterwards, and will probably not affect users who cannot fix it - but it would be elegant if it just worked automatically, and it is probably a rather small change. I attach my menu.lst post-install of 2.6.27-14 - I cannot see the actual file attached to the original bug report. The 3-way merge does not seem to have touched anything in the file, but the kernel has been installed in /boot, and manually adding a menu entry works fine.

[dbarnett (dhbarnett)]

The big issue here is not that the three way merge wasn't successful. It's that the installer fails to continue cleanly after the failure. it claims a failure and looks like it's trying to clean up when really it's sitting there with a blank terminal screen. I had to ctrl-c in the terminal and then it continued on (also unsuccessfully, but then it worked when I tried again).

The recovery from failure should be more graceful.

[Leann Ogasawara (leannogasawara)]

This is a duplicate of bug 269539 so I am marking it as such. Please continue to track this issue at that report. Thanks.