[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kscreensaver] [Bug 224200] multiple kblankscrn.kss in memory
From:       Peter Yellman <forshopping () webformation ! com>
Date:       2014-04-03 18:16:48
Message-ID: bug-224200-17878-ahXM4KpfjN () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=224200

--- Comment #36 from Peter Yellman <forshopping@webformation.com> ---
I can confirm the following behavior in KDE 4.11.3 with these settings:

X Start automatically after (1 minute)
X Require password after (10 seconds)

If I interrupt/wake the screen after 1 minute but before 70 seconds no password
dialog is presented, and an "orphan" kblankscrn.kss process gets left behind.
If I wait 70+ seconds, I receive a login dialog and there is no orphan process.

I do not normally use the "Require password after" setting at all, I just leave
it unchecked, and the orphan processes really build up.  I had observed in the
past that when I manually trigger the screen lock/password with CTRL+ALT+L,
there was never an orphan process left behind.

On another note, I'm not a big fan of the terminology "screen locker" here. 
Why not just screen saver, like everyone is used to?
(In reply to comment #35)
> (In reply to comment #34)
> > Yes, using Kubuntu Trusty Beta with KBlankscreen 4.11.8 and KDE 4.12.95 I
> > set the Screen Locker to start automatically after 1 minute and require
> > password after 10 seconds. When the password is required (after the timeout,
> > or manually locking the screen), no screensaver process remains. If I hit
> > the keyboard when the screensaver starts, before the password is required, a
> > kblankscrn.kss process does remain afterwards.
> Thanks for the confirmation.
> I'm pretty sure that my patch would fix the issue for you then, too.
> 
> But I really would like to have some feedback from at least one of the other
> posters in this bug report as well, please.

I can confirm the following behavior in KDE 4.11.3 with these settings:

X Start automatically after (1 minute)
X Require password after (10 seconds)

If I interrupt/wake the screen after 1 minute but before 70 seconds, no
password dialog is presented and an "orphan" kblankscrn.kss process gets left
behind.
If I wait 70+ seconds, I receive a login dialog and there is no orphan process.

I don't normally use the "Require password after" setting at all (I just leave
it unchecked) and the orphan processes really build up.  I had observed in the
past that when I manually trigger the screen lock w/password with CTRL+ALT+L,
there was never an orphan process left behind.

Side note, I'm not a big fan of the terminology "screen locker" for this
functionality.  Why not just screen saver, like everyone is used to?

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]