Package: vlock Version: 2.2.2-3 Severity: important Dear Maintainer,
I start X with startx from the console, my .xsession contains: xautolock -locker "vlock -san" & [shortend version, not all options shown] After some idle time xautolock executes vlock -san which in turn locks the screen. This is fine. I can unlock the screen fine too. But sometimes vlock does not exit after unlocking the screen. I then see vlock-main in the output of ps fax. One would not realise this, but xautolock will not execute vlock after idle time because xautolock "thinks" vlock is still running. I was never able to reproduce circumstances which lead to this situation but it happens quite often (up to a few times a day) and for several moths now (perhaps even over a year -- I was too lazy to file bug until now). When I willingly leave the computer I check via ps fax if vlock-main is in the output and if so kill it. But often I forget to do this. This is a security problem, therefore I choose severity important for this bug report. vlock should always exit after unlocking the screen. Thanks for your attention, Gregor -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vlock depends on: ii adduser 3.113+nmu3 ii libc6 2.13-38 ii libpam-modules 1.1.3-7.1 ii libpam0g 1.1.3-7.1 vlock recommends no packages. vlock suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
