On Fri, 12 Apr 2024 at 14:00, Chris Hofstaedtler <z...@debian.org> 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 happening behind the scenes during encrypted hd unlock and how to figure out "what wants it" :-( ) I basically inputted a password (both on the "UI" and the console after ctrl-alt-del) and on the console it showed me that error after pressing enter. It then showed the passwort entry box/line again. Given that it was the password validation, I figured I should file a bug here. Jan
