[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:       Wolfgang Bauer <wbauer () tmo ! at>
Date:       2014-04-24 22:28:34
Message-ID: bug-224200-17878-c55IqU4vwm () http ! bugs ! kde ! org/
[Download RAW message or body]

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

Wolfgang Bauer <wbauer@tmo.at> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
   Version Fixed In|4.10.2                      |4.11.9
         Resolution|---                         |FIXED
      Latest Commit|http://commits.kde.org/kde- |http://commits.kde.org/kde-
                   |workspace/ee003f90c6251e8c7 |workspace/26a8ddc018d940ea1
                   |3928127ab91945fc46fa3a0     |910ced6264344b520ad8405

--- Comment #51 from Wolfgang Bauer <wbauer@tmo.at> ---
Git commit 26a8ddc018d940ea1910ced6264344b520ad8405 by Wolfgang Bauer.
Committed on 24/04/2014 at 22:25.
Pushed by wbauer into branch 'KDE/4.11'.

screenlocker: don't leave behind screensaver processes

Currently the screen locker just kills the greeter (kscreenlocker_greet)
when the screen is unlocked by the user during the grace time.
But apparently this can leave behind running screensaver processes
launched by the greeter, see the bug report (which has the highest
number of votes of all open bugs AFAICS).

This patch changes this to only terminate the greeter, and adds a signal
handler to the greeter to exit gracefully in this case.
The signal handler exits with return code 1, so that it is not possible
to circumvent the password input by just sending a SIGTERM. (the screen
locker restarts the greeter in case it doesn't quit with exit code 0)
FIXED-IN: 4.11.9
REVIEW: 117644

M  +13   -1    ksmserver/screenlocker/greeter/main.cpp
M  +1    -1    ksmserver/screenlocker/ksldapp.cpp

http://commits.kde.org/kde-workspace/26a8ddc018d940ea1910ced6264344b520ad8405

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