I can not anymore reproduce the issue anymore: while trying to capture
the full error message, I created an initrd without libgcc_s in it and
it booted up. Below I added some--hopefully relevant-- parts of the
dpkg log and original requested phread output, maybe that still sheds
some light on this.
On Fri, 12 Apr 2024 at 14:00, Chris Hofstaedtler wrote:
> Can you tell us which part was wanting libgcc_s.so.1?
> cryptsetup in the initramfs doesn't seem to be the (original)
> problem of that.
How would I find out? (I've never debugged such a problem, and have
basically no clue what is happenin
Package: cryptsetup
Version: 2:2.7.2-1
Severity: normal
Dear Maintainer,
After a recent apt upgrade on a debian sid system (installed about 3
years ago with an installer, choosing to encrypt the filesystem, no
idea what actually ended up on my system as a crypt setup. Since then,
the laptop runs
Subject: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1
Package: cryptsetup
Version: 2:2.7.2-1
Severity: normal
Dear Maintainer,
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
4 matches
Mail list logo
