On 2019-04-15 23:07:02 +0200, Sven Hartge wrote: > In my case the reason was fc-cache was failing because of a very very > old directory /usr/X11R6/lib/X11 containing old left over fonts.
I don't have such a directory. /usr/X11R6 doesn't even exist. But... > Could you add "set -x" to the top of > /usr/share/initramfs-tools/hooks/plymouth to get a clear picture where > exactly the hook fails? It is also fc-cache that is failing: [...] + ln -rs /var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 /var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu/libbsd.so.0 + target=/usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 + [ -e /var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 ] + mkdir -p /var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu + [ n = y ] + cp -pP /usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 /var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 + cp -a /usr/share/plymouth/themes/details /var/tmp/mkinitramfs_0BRFs9//usr/share/plymouth/themes + cp -a /usr/share/plymouth/themes/text /var/tmp/mkinitramfs_0BRFs9//usr/share/plymouth/themes + [ -f /etc/os-release ] + cp /etc/os-release /var/tmp/mkinitramfs_0BRFs9/etc + cp /usr/share/plymouth/debian-logo.png /var/tmp/mkinitramfs_0BRFs9/usr/share/plymouth + mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d + cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts + cp -rL /etc/fonts/conf.d/60-latin.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d + mkdir -p /var/tmp/mkinitramfs_0BRFs9/var/cache/fontconfig + mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/local/share/fonts + [ -e /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf ] + mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu + cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu + cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu + fc-cache -s -y /var/tmp/mkinitramfs_0BRFs9 E: /usr/share/initramfs-tools/hooks/plymouth failed with return 134. 134 corresponds to SIGABRT, which is not a normal termination (even in case of error). Thus I would assume that it is a bug in fc-cache. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
