[pkg-cryptsetup-devel] Bug#1068848: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

[Wesley Schwengle]

Hi

On Fri, Apr 12, 2024 at 09:04:23AM +0200, Jan Katins wrote:
> Subject: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1
> Package: cryptsetup
> Version: 2:2.7.2-1
> Severity: normal
> 
> After a recent apt upgrade, my system failed to unlock. After a
> ctrl-alt-del, I got to the console and there it showed an error about
> libgcc_s.so.1 not available and aborting.
> 
> Thankfully, I still had a other initrd around (I guess due to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065698, yay for
> bugs!).
> 
> I snooped around in the source code a bit and found that libgcc_s
> seems to be dlopened and is special cased:
> https://salsa.debian.org/kernel-team/initramfs-tools/-/blob/master/hook-functions?ref_type=heads#L248-249
> (original bugreport:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254). So my guess
> is that nothing depends on libpthread either anymore, and this is the
> case: `lsinitramfs initrd.img-6.7.9-amd64 |grep thread` shows no
> libpthread (actually nothing). I fixed it now by installing a
> update-initramfs hook (thanks to
> https://groups.google.com/g/linux.debian.bugs.dist/c/4fi2HaOEC_M):

I had the same issue a while back, because of the t64 transitioning I chaulked
it up to that. I fixed it as described in Ubuntu bug:

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594

Cheers,
Wesley