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

2024-04-26 Thread Christoph Anton Mitterer
On Sat, 2024-04-27 at 03:15 +0200, Guilhem Moulin wrote: > Yup that'd make sense to me (and I see you did that already), thanks! :-) Unfortunately I doubt it will be possibly to do some fully generic solution. So best we'll get is probably either an unconditional inclusion or some simpler copy_*

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

2024-04-26 Thread Guilhem Moulin
On Sat, 27 Apr 2024 at 02:07:21 +0200, Christoph Anton Mitterer wrote: > So you say it's a glibc thingy, that this doesn't show up anymore? Yup, that's what I wrote https://bugs.debian.org/1032235#97 | It was intentional, see the article | https://developers.redhat.com/articles/2021/12/17/why-gl

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

2024-04-26 Thread Christoph Anton Mitterer
On Sat, 2024-04-27 at 01:48 +0200, Guilhem Moulin wrote: > built using glibc ≥2.34.  AFAICT the “if the ldd output includes > libpthread then run copy_libgcc()” logic from initramfs-tools is > mostly moot > now Ah, I just realised glibc "merged" libpthread ^^ Therefore... > but despite what I pr

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

2024-04-26 Thread Christoph Anton Mitterer
Hey Guilhem On Sat, 2024-04-27 at 01:48 +0200, Guilhem Moulin wrote: > Even it weren't, libpthread wouldn't show up since src:argon2 from > bookworm > and later is built using glibc ≥2.34. When argon2 builds, it uses -pthread ... not really sure what that does exactly, the manpage merely says it

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

2024-04-26 Thread Guilhem Moulin
Hi, On Sat, 27 Apr 2024 at 00:33:51 +0200, Christoph Anton Mitterer wrote: > Now the problem is that argon2 is statically linked, so there's no > libpthread showing up in its ldd, and thus copy_exec doesn't realise it > needs to invoke copy_libgcc. Even it weren't, libpthread wouldn't show up sin

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

2024-04-26 Thread Christoph Anton Mitterer
Hey guys. I kinda ran into a similar issue. I use my own OpenPGP keyscript which is highly improved upon that ("decrypt_gnupg") shipped by the package. One thing that I do is offer optionally feeding the entered passphrase trough argon2 (the standalone tool from the package of the same name) whi

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

2024-04-14 Thread Guilhem Moulin
Control: reopen -1 Control: tag -1 - unreproducible moreinfo On Sun, 14 Apr 2024 at 21:26:25 +0200, Guilhem Moulin wrote: > At this point something triggered rebuilding a new initramfs image, but > that's not src:cryptsetup as none of its binary packages have been > upgraded yet. On second though

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.

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

2024-04-12 Thread Guilhem Moulin
On Fri, 12 Apr 2024 at 14:37:16 +0200, Guilhem Moulin wrote: > What is that “GUI” view? src:cryptsetup doesn't provide that, I wonder > if it might be what needs libphtread. FWIW, I later noticed you used a splash screen (plymouth) and thought it might be because of that, but I still cannot repro

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

2024-04-12 Thread Guilhem Moulin
Control: tag -1 + unreproducible moreinfo On Fri, 12 Apr 2024 at 12:45:09 +0200, Milan Broz wrote: > Just FYI (for upstream code): if cryptsetup/libcryptsetup is linked with > OpenSSL >= 3.2, > it does not need libphtread (as threads are implemented in OpenSSL for Argon2 > internally). Thanks f

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 happenin

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

2024-04-12 Thread Chris Hofstaedtler
On Fri, Apr 12, 2024 at 09:11:51AM +0200, Jan Katins wrote: > 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

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

2024-04-12 Thread Milan Broz
On 4/12/24 9:11 AM, Jan Katins wrote: 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

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

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