package linux-image-3.9.0-2-generic 3.9.0-2.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[David Henningsson]

[Impact]

An upgrade from Raring to Saucy fails with an error about initramfs-tools' postinst. The automatic repair functionality fixes the problem, but then the PostUpgrade tasks in the upgrade do not run.

[Original Description]
Unsure how this happened, and it seems to have fixed itself too with a dist-upgrade.

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: linux-image-3.9.0-2-generic 3.9.0-2.7
ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
Uname: Linux 3.9.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu1
AptOrdering:
 initramfs-tools: Configure
 linux-image-3.9.0-2-generic: Configure
 linux-image-extra-3.9.0-2-generic: Configure
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: david 1986 F.... pulseaudio
Date: Tue May 28 12:23:04 2013
DuplicateSignature: package:linux-image-3.9.0-2-generic:3.9.0-2.7:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
HibernationDevice: RESUME=UUID=fa2ccdc6-c068-4438-8815-593002a38c7e
InstallationDate: Installed on 2013-05-08 (20 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
MachineType: Hewlett-Packard HP ProBook 4520s
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-2-generic root=UUID=a5d6e01c-ed1a-49a2-934c-271f53d20520 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions: grub-pc 2.00-14ubuntu1
SourcePackage: initramfs-tools
Title: package linux-image-3.9.0-2-generic 3.9.0-2.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/29/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68AZZ Ver. F.08
dmi.board.name: 1413
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 57.1D
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68AZZVer.F.08:bd06/29/2010:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1413:rvrKBCVersion57.1D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4520s
dmi.sys.vendor: Hewlett-Packard

[Brian Murray (brian-murray)]

Moving to plymouth:

cp: cannot stat ‘/module-files.d/libpango1.0-0.modules’: No such file or directory
cp: cannot stat ‘/modules/pango-basic-fc.so’: No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.

[Steve Langasek (vorlon)]

This bug has already been fixed in the latest version of Plymouth in saucy.

[Robie Basak (racb)]

I can see that a change that affects this issue was made in 0.8.8-0ubuntu7 - presumably this is where this bug was fixed?

I hit this with an upgrade from Raring to Saucy just now. The upgrade is still in progress; plymouth is still on 0.8.8-0ubuntu6.1 and hasn't been upgraded yet.

The bug caused a popup window telling me that the initramfs-tools postinst failed.

Given that this affects the upgrader UX, would it be an idea to SRU this to affected releases? Otherwise people upgrading from Raring to Saucy will hit this if plymouth isn't upgraded early enough in the process.

[Steve Langasek (vorlon)]

It can't be SRUed. With the old pango, plymouth needs to unconditionally copy the modules. With the new pango, plymouth needs to never copy the modules. I thought this was being addressed by having the new libpango-1.0-0 declare a Breaks: on the old plymouth, but that doesn't seem to be the case.

And thinking about it, I believe we need a versioned Conflicts:, not a versioned Breaks:, to ensure unpack order.

So, reopening and reassigning this bug to pango1.0.

[Sebastien Bacher (seb128)]

Steve, is that just a Conflicts to add then?

@pitti: Ccing you on the bug since you got the new pango in and followed more that transition than me, I'm not sure what is needed there (but I'm happy to upload with a Conflicts if you/Steve says it's the right fix)

[Launchpad Janitor (janitor)]

This bug was fixed in the package pango1.0 - 1.32.5-5ubuntu1

---------------
pango1.0 (1.32.5-5ubuntu1) saucy; urgency=low

  * Add a versioned conflicts on old versions of plymouth whose initramfs
    hook tries to find pango modules. LP: #1185300.
 -- Steve Langasek <email address hidden> Tue, 11 Jun 2013 10:30:50 -0700