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 for confirming! We're now linking with OpenSSL 3.2 indeed, and our CI confirms that unlocking works in that environment. 2:2.7.2-1 builds with OpenSSL 3.2 *and* removes the libgcc_s/libargon2 workaround from the initramfs hook: https://tracker.debian.org/news/1517996/accepted-cryptsetup-2272-1-source-into-unstable/ >> It would also be nice if the "gui" view could show the error or at >> least tell the user to pres ctrl-alt-del to get to a more informative >> view, took me ages to figure out that one :-( What is that “GUI” view? src:cryptsetup doesn't provide that, I wonder if it might be what needs libphtread. Otherwise, my guess is a race where the 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? If you still have the broken initramfs image, please extract it with `unmkinitramfs /path/to/broken.initrd.img /path/to/destdir` and try to find which executable / shared library needs libphtread, for instance with cd /path/to/destdir for p in $(find -P {usr/,}lib/x86_64-linux-gnu {usr/,}{,s}bin/ -type f); do objdump -p "$p" 2>/dev/null | grep -q pthread && echo "$p"; done This will hopefully shed some light on this. -- Guilhem.
signature.asc
Description: PGP signature
