| Summary: | Notification of screensaver termination | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreensaver | Reporter: | Tvrtko A. Ursulin <tvrtko.ursulin> | 
| Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> | 
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | alther, l.lunak | 
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| 
        
          Description
        
        
          Tvrtko A. Ursulin
        
        
        
        
          2004-05-10 16:00:07 UTC
        
       It's not very well documented (as in, not at all), but what when screen saver ends, it sends a SIGTERM signal to the actual screen saver process (your process). You need to implement a SIGTERM handler to catch the signal and do whatever it is you need to do before ending. Having said that, there is a serious race condition bug that I just reported (bug 81380) which may very well kill your process before you have a chance to completely clean up. |