Package: lvm2-lockd Version: 2.03.11-1 Severity: grave Justification: renders package unusable
Dear Maintainer, after the update of lvm2 packages to version 2.03.11-1 in sid, the lvmlockd.service fails to start and just hangs till systemctl times out and exits with an error. The previous version worked flawlessly on my laptop. Please let me know if there are any checks I can do to help nailing down the problem, and/or any relevant configuration details that I can provide. Thanks in advance, best regards Giacomo Mulas -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.4-jak (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it_IT,en_EN Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lvm2-lockd depends on: ii libc6 2.31-9 ii libdlm3 4.0.9-2 ii libsanlock-client1 3.8.2-1+b2 ii libselinux1 3.1-2+b2 ii libudev1 247.2-4 ii lvm2 2.03.11-1 lvm2-lockd recommends no packages. lvm2-lockd suggests no packages. -- no debconf information
