Hello, This bug, as sent by the issuer, seems quite specific to xautolock: > One would not realise this, but xautolock will not execute vlock > after idle time because xautolock "thinks" vlock is still > running.
Not sure of this statement due to https://bugs.debian.org/702705#72 However, if "vlock -n" still works even if another vlock-main process is running, then maybe the "new.so" plugin / module should be reinstated, with a warning or a KNOWN BUG section in documentation. Even if it means piling up processes (yes, it does worth it). >From what I know, there is no Debian Jessie alternative to "vlock -n" (locking system, not only X session, from X). This behavior is still usefull when mapping a shortcut (the Windows "Win+l"). For the following readers who are looking for a short term solution, none of "similar packages" from Debian page [https://packages.debian.org/jessie/vlock] - pessulus - python-pushy - libdbd-anydata-perl - away - qingy - ttyd - cereal - vde2 - xlockmore-gl - xlockmore - ngetty seems to provide this feature. The only solution I can think about, is to open a virtual console (Ctrl+Alt+F4 for instance) after logging ; and when leaving keyboard, switch back to this console and run "vlock -a". "alias l=vlock -a" for lazy persons like me ;-) PS: I do not expect an answer, my purpose is just to feed back. -- Stevens LION -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
