Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-14 Thread Jan Katins
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. If not I guess this can be closed.

On Fri, 12 Apr 2024 at 16:23, Guilhem Moulin  wrote:
> FWIW, I later noticed you used a splash screen (plymouth) and thought it

yes, sorry: GUI = Splash screen

> Otherwise, my guess is a race where the initramfs image was somehow
> rebuilt before libcryptsetup12 was upgraded, but AFAICT the dependencies
> are properly set to avoid that.  Does the broken initramfs image contain
> libargon2.so, if so does its libcryptsetup12 use it?

According to `lsinitramfs initrd.img-6.7.9-amd64 |grep libargon2.so`
it's not used.

I've saved away the dpkg.log and this is an excerpt (via `rg "trigproc
initramfs-tools|libcryptsetup12|libargon2|libssl3t64|libc6|libglib2|libgcc"
~/tmp/dpkg.log`) with added output from `rg "Start-Date|Commandline"
/var/log/apt/history.log`. The last two initramfs-tools trigger calls
should correspond to me trying to fix the problem by reinstalling some
packages and maybe not even realizing it's already fixed by the
dist-upgrade?

2:Start-Date: 2024-04-10  11:30:00
3:Commandline: apt upgrade -y
7:End-Date: 2024-04-10  11:33:19

87:2024-04-10 11:30:04 upgrade libgcc-13-dev:amd64 13.2.0-18 13.2.0-23
88:2024-04-10 11:30:04 status half-configured libgcc-13-dev:amd64 13.2.0-18
89:2024-04-10 11:30:04 status unpacked libgcc-13-dev:amd64 13.2.0-18
90:2024-04-10 11:30:04 status half-installed libgcc-13-dev:amd64 13.2.0-18
91:2024-04-10 11:30:04 status unpacked libgcc-13-dev:amd64 13.2.0-23
107:2024-04-10 11:30:06 upgrade libgcc-12-dev:amd64 12.3.0-15 12.3.0-17
108:2024-04-10 11:30:06 status half-configured libgcc-12-dev:amd64 12.3.0-15
109:2024-04-10 11:30:06 status unpacked libgcc-12-dev:amd64 12.3.0-15
110:2024-04-10 11:30:06 status half-installed libgcc-12-dev:amd64 12.3.0-15
111:2024-04-10 11:30:06 status unpacked libgcc-12-dev:amd64 12.3.0-17
158:2024-04-10 11:30:07 upgrade libgcc-s1:amd64 14-20240303-1 14-20240330-1
159:2024-04-10 11:30:07 status half-configured libgcc-s1:amd64 14-20240303-1
160:2024-04-10 11:30:07 status unpacked libgcc-s1:amd64 14-20240303-1
161:2024-04-10 11:30:07 status half-installed libgcc-s1:amd64 14-20240303-1
162:2024-04-10 11:30:07 status unpacked libgcc-s1:amd64 14-20240330-1
164:2024-04-10 11:30:07 configure libgcc-s1:amd64 14-20240330-1 
165:2024-04-10 11:30:07 status unpacked libgcc-s1:amd64 14-20240330-1
166:2024-04-10 11:30:07 status half-configured libgcc-s1:amd64 14-20240330-1
167:2024-04-10 11:30:07 status installed libgcc-s1:amd64 14-20240330-1
210:2024-04-10 11:30:08 upgrade libc6-dev:amd64 2.37-15.1 2.37-16
211:2024-04-10 11:30:08 status half-configured libc6-dev:amd64 2.37-15.1
212:2024-04-10 11:30:08 status unpacked libc6-dev:amd64 2.37-15.1
213:2024-04-10 11:30:08 status half-installed libc6-dev:amd64 2.37-15.1
214:2024-04-10 11:30:08 status unpacked libc6-dev:amd64 2.37-16
235:2024-04-10 11:30:09 upgrade libc6:amd64 2.37-15.1 2.37-16
236:2024-04-10 11:30:09 status half-configured libc6:amd64 2.37-15.1
237:2024-04-10 11:30:09 status unpacked libc6:amd64 2.37-15.1
238:2024-04-10 11:30:09 status half-installed libc6:amd64 2.37-15.1
239:2024-04-10 11:30:09 status unpacked libc6:amd64 2.37-16
241:2024-04-10 11:30:09 configure libc6:amd64 2.37-16 
242:2024-04-10 11:30:09 status unpacked libc6:amd64 2.37-16
243:2024-04-10 11:30:09 status half-configured libc6:amd64 2.37-16
244:2024-04-10 11:30:10 status installed libc6:amd64 2.37-16
755:2024-04-10 11:30:33 upgrade libgcc-11-dev:amd64 11.4.0-7 11.4.0-8
756:2024-04-10 11:30:33 status half-configured libgcc-11-dev:amd64 11.4.0-7
757:2024-04-10 11:30:33 status unpacked libgcc-11-dev:amd64 11.4.0-7
758:2024-04-10 11:30:33 status half-installed libgcc-11-dev:amd64 11.4.0-7
759:2024-04-10 11:30:34 status unpacked libgcc-11-dev:amd64 11.4.0-8
951:2024-04-10 11:30:43 status triggers-pending libglib2.0-0:amd64 2.78.4-1
1491:2024-04-10 11:31:04 upgrade libglib2.0-data:all 2.78.4-4 2.78.4-6
1492:2024-04-10 11:31:04 status half-configured libglib2.0-data:all 2.78.4-4
1493:2024-04-10 11:31:04 status unpacked libglib2.0-data:all 2.78.4-4
1494:2024-04-10 11:31:04 status half-installed libglib2.0-data:all 2.78.4-4
1495:2024-04-10 11:31:04 status unpacked libglib2.0-data:all 2.78.4-6
2711:2024-04-10 11:32:13 configure libglib2.0-data:all 2.78.4-6 
2712:2024-04-10 11:32:13 status unpacked libglib2.0-data:all 2.78.4-6
2713:2024-04-10 11:32:13 status half-configured libglib2.0-data:all 2.78.4-6
2714:2024-04-10 11:32:13 status installed libglib2.0-data:all 2.78.4-6
3527:2024-04-10 11:32:42 configure libgcc-12-dev:amd64 12.3.0-17 
3528:2024-04-10 11:32:42 status unpacked libgcc-12-dev:amd64 12.3.0-17
3529:2024-04-10 11:32:42 status half-configured libgcc-12-dev:amd64 12.3.0-17
3530:2024-04-10 11:32:42 s

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Jan Katins
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 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