Package: xautolock Version: 1:2.2-8 Severity: critical This may be related to #1022781 or not.
I have xautolock running: % ps -fC xautolock UID PID PPID C STIME TTY TIME CMD madduck 2733 2421 0 May05 ? 00:00:53 xautolock -time 3 -locker xsecurelock && autorandr -- … and yet: % xautolock -locknow % echo $? 0 It exits 0, but nothing happens. If I use strace on the main process, there is also zero activity reported. Moreover, despite being set to lock after 3 minutes, the main xautolock process does not lock the display. This has happened multiple times, and each time, only a restart of the main xautolock process makes things work again. So if I don't restart the process regularly (daily? hourly?), then occasionally, the system will not lock as expected, and that is a huge security problem, hence the critical severity. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xautolock depends on: ii libc6 2.37-17 ii libx11-6 2:1.8.7-1 ii libxext6 2:1.3.4-1+b1 ii libxss1 1:1.2.3-1 Versions of packages xautolock recommends: ii suckless-tools 47-1 xautolock suggests no packages. -- debconf-show failed -- .''`. martin f. krafft <madduck@d.o> : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems
