Bug 222200 - Can not unlock screen if passphrase dialog was cancelled once
Summary: Can not unlock screen if passphrase dialog was cancelled once
Status: RESOLVED DUPLICATE of bug 218763
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-11 12:19 UTC by Rolf Eike Beer
Modified: 2010-02-15 00:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Eike Beer 2010-01-11 12:19:03 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

This has been there for a while (since at least RC2): lock the screen, make the password dialog appear, press cancel. Afterwards you can move the mouse, click around or do anything: the password dialog will never show up again. This is with plasma applets on screensaver if that makes any difference.

My way to get in is
-switch to console mode
-killall kscreenlocker
-switch back

I think I also sometimes get it the same behaviour when the dialog times out and I have already typed something but I can't reproduce this.
Comment 1 Chani 2010-01-11 20:34:49 UTC
have you tried hitting the esc key? I've never had trouble unlocking my screen.

also, get the latest rc, then delete your plasma-overlay-appletsrc (or set the containment's plugin=saverdesktop if you don't want to lose your widgets).
Comment 2 Rolf Eike Beer 2010-01-11 21:14:39 UTC
Hm, yes, escape helps. It was just totally unusual that mouse moving did not bring up the password dialog again. Don't know if that is intended.

After filing the bug I had it one more time that the password dialog disappeared even if I did not press cancel or escape after I had started typing the password. After that mouse movement did not bring it up, too.
Comment 3 Oswald Buddenhagen 2010-02-15 00:42:15 UTC

*** This bug has been marked as a duplicate of bug 218763 ***