Um 01:35 Uhr am 16.04.19 schrieb Vincent Lefevre:
> On 2019-04-15 23:07:02 +0200, Sven Hartge wrote:

>> 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:

> + 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.

Try running the following commands as root:

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
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 -v -s -y /var/tmp/mkinitramfs_0BRFs9

It uses the same commands from the bash trace, but added "-v" to the
fc-cache call, to exactly see what it is choking on. This got me to
/usr/X11R6/lib/X11 in my case (which just shows how old the installation
on my workstation is).

If this is inconclusive, add "strace -f" to the fc-cache call, maybe even
gdb, if you know how to use it.

Sidenote here: something is very brittle about fc-cache. I had to debug
and fix more fc-cache and fontconfig issues in the last years using Debian
Sid than I had other issues.

Grüße,
Sven.

Reply via email to