From kde-bugs-dist  Sat Aug 31 19:33:00 2002
From: owner () bugs ! kde ! org (Stephan Kulow)
Date: Sat, 31 Aug 2002 19:33:00 +0000
To: kde-bugs-dist
Subject: Bug#28688: marked as done (matrix screensaver locking when user has no password) by Ryan Cumming <ry
X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=103082244622369

Your message with subj: matrix screensaver locking when user has no password

Thank you for your bug report.
This bug/feature request has already been reported, and this report will
be marked as a duplicate.

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'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

(Complete bug history is available at http://bugs.kde.org/db/28/28688.html)

Received: (at submit) by bugs.kde.org; 11 Jul 2001 05:10:37 +0000
Received: (qmail 1516 invoked by uid 33); 11 Jul 2001 05:10:37 -0000
Date: 11 Jul 2001 05:10:37 -0000
Message-ID: <20010711051037.1515.qmail@master.kde.org>
To: submit@bugs.kde.org
Subject: matrix screensaver locking when user has no password
From: raspl@gmx.de

Package:           kscreensaver
Version:           KDE 2.1.1 
Severity:          normal
Installed from:    SuSE RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Plain SuSE rpms

Do the following:
* create a user without(!) a password
* start kde
* select the matrix screensaver
* hit the symbol to lock the screen
* try to unlock the screen...
It is not possible to get out of the locked screen once it has been locked. One might expect that simply hitting <return> will do, but it does not! I didn't try it out with a different screensaver, but I guess this is a general problem.

(Submitted via bugs.kde.org)