Your message dated Tue, 11 Sep 2007 20:38:00 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Fwd: Bug#441861: vlock: locked system is unreachable until
rebooted
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: vlock
Version: 2.0-4
Severity: serious
When locking terminal with `xscreensaver-command -lock', no screensaver
is run. Instead, the console becomes black and any keyboard input is
displayed in unreadable way. Computer is unusable until rebooted.
Downloading vlock to 1.3-10 fixes the problem.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages vlock depends on:
ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
ii libpam-modules 0.99.7.1-4 Pluggable Authentication Modules f
ii libpam0g 0.99.7.1-4 Pluggable Authentication Modules l
vlock recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
---------- Forwarded message ----------
From: Valery V. Vorotyntsev <[EMAIL PROTECTED]>
Date: Sep 11, 2007 8:34 PM
Subject: Re: Bug#441861: vlock: locked system is unreachable until rebooted
To: Alexander Wirt <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
On 9/11/07, Alexander Wirt <[EMAIL PROTECTED]> wrote:
> I don't understand you problem. xcreensaver-command has nothing to do with
> vlock (at least not per default). So when gots vlock called with which
> parameters?
>
> I use it with xautolock here: xautolock -locker 'vlock -a -n'. Which works
> fine.
Yes. You are right.
I retried vlock_2.0-4 and everything went fine. There is something else
causing my problem.
Sorry for inconvenience.
--
WBR,
vvv
--- End Message ---
