Bug#679687: plymouth: initramfs hook fails to find renderers with multi-arch
Hi, I am also hit by this bug, it seems: During the upgrade I just ran on my Debian unstable machine, I got this error: update-initramfs: Generating /boot/initrd.img-3.2.0-3-amd64 E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-3.2.0-3-amd64 with 1. leaving the kernel and the initramfs-tools package unconfigured. Interesting enough, purging and re-installing plymouth fixed the problem (maybe because the default theme changed to text?). Running plymouth-set-theme does not work either: $ sudo plymouth-set-default-theme solar -R /usr/lib/x86_64-linux-gnu/plymouth/plymouth-update-initrd: line 2: mkinitrd: command not found Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679687: plymouth: initramfs hook fails to find renderers with multi-arch
Package: plymouth Version: 0.8.5.1-2 Severity: important Plymouth installs a hook for mkinitramfs in /usr/share/initramfs-tools/hooks/, which fails on multi-arch systems, since the two lines copy_exec /usr/lib/plymouth/renderers/frame-buffer.so copy_exec /usr/lib/plymouth/renderers/drm.so no longer point at the right place: on my system, they should probably be copy_exec /usr/lib/i386-linux-gnu/plymouth/renderers/frame-buffer.so copy_exec /usr/lib/i386-linux-gnu/plymouth/renderers/drm.so respectively. There are already lines that detect multi-arch for pango above: presumably we could just use the same technique. Rupert -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.3.0+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages plymouth depends on: ih initramfs-tools0.106 ii libc6 2.13-34 ii multiarch-support 2.13-34 plymouth recommends no packages. plymouth suggests no packages. -- Configuration Files: /etc/plymouth/plymouthd.conf changed: [Daemon] Theme=joy -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679687: plymouth: initramfs hook fails to find renderers with multi-arch
This package seems to have similar initramfs-hooks problems on amd64, and the only solution I've found is to revert to plymouth 0.8.5.1-1. Perhaps someone more knowledgeable than myself would consider whether this warrants escalation to grave. update-initramfs: deferring update (trigger activated) Setting up plymouth (0.8.5.1-2) ... Installing new version of config file /etc/init.d/plymouth ... update-initramfs: deferring update (trigger activated) Setting up plymouth-drm (0.8.5.1-2) ... Setting up pciutils (1:3.1.9-5) ... Setting up libc-dev-bin (2.13-34) ... Setting up libc6-dev:amd64 (2.13-34) ... Setting up libc6-i386 (2.13-34) ... Setting up libc6-dev-i386 (2.13-34) ... Setting up plymouth-x11 (0.8.5.1-2) ... Setting up plymouth-dev (0.8.5.1-2) ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-3-amd64 live-boot: core filesystems devices utils udev wget blockdev. E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-3.2.0-3-amd64 with 1. dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679687: plymouth: initramfs hook fails to find renderers with multi-arch
severity 679687 grave thanks dj_palindrome wrote (30 Jun 2012 23:11:14 GMT) : This package seems to have similar initramfs-hooks problems on amd64, and the only solution I've found is to revert to plymouth 0.8.5.1-1. Perhaps someone more knowledgeable than myself would consider whether this warrants escalation to grave. Fails here too. I don't see how the package can be usable with this bug, so I'm bumping the severity to grave. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
