[MPlayer-dev-eng] [PATCH] [trivial] xautolock based screensaver enable\disable by -stop-xscreensaver
rcooley at spamcop.net
Mon Sep 13 14:44:11 CEST 2004
On Sat, 11 Sep 2004 22:28:20 +0900
Attila Kinali <attila at kinali.ch> wrote:
> we end up enabling something that wasnt running at all.
No. 'xautolock -enable' doesn't work that way. If there isn't another
instance of xautolock running (in daemon mode) then xautolock -enable
will only report an error. It won't start-up xautolock.
I can think of 2 other issues with this, however.
1) Upon quiting, sometimes mplayer silently keeps running in the
background. This is a terrible security problem.
2) If you've run 'xautolock -disable' before you run mplayer (for some
other reason), it will re-enable it, even if you don't want it enabled.
I use xautolock, and I will disable this functionality in my own builds.
Using xautolock with the "corners" options is a much better solution.
More information about the MPlayer-dev-eng