[MPlayer-dev-eng] [PATCH] [trivial] xautolock based screensaver enable\disable by -stop-xscreensaver
Attila Kinali
attila at kinali.ch
Wed Sep 15 03:23:29 CEST 2004
On Mon, Sep 13, 2004 at 05:44:11AM -0700, rcooley wrote:
> On Sat, 11 Sep 2004 22:28:20 +0900
> Attila Kinali <attila at kinali.ch> wrote:
>
> > otherwise
> > 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.
Ok.
> 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.
Can you reproduce that ? If so, please try to find out why
MPlayer keeps running. It should never do taht.
(Actualy i cannot think of any reason how it could do that)
> 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.
Is it possible to check for this case ?
Attila Kinali
More information about the MPlayer-dev-eng
mailing list