Package: physlock Followup-For: Bug #987945 Dear Maintainer, I'm currently not able to reproduce the behaviour (hat some updates in between and dpkg-reconfigured again), anyway the context is: X.org, i3, /usr/bin/physlock -sdm, (just using the same KB as on the first message). Disconecting/connecting the external KB doesn't seems to trigger the issue either. Please feel free to close the issue, if somehow happens again I'll try harder trying to reproduce.
Thanks for your time! xiscu -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (10, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages physlock depends on: ii libc6 2.31-11 ii libpam0g 1.4.0-7 ii libsystemd0 247.3-5 physlock recommends no packages. physlock suggests no packages. -- no debconf information
