While playing a game (Vega Strike) I was surprised by the screen saver popping in every while. It
does not detect my keypresses during the game, apparently.
The game goes then totally black. I press a key, and I get the game in a smaller window, and the
screensaver dialog asking for my password.
Weird.
I’d like to know if we know of a way to inhibit the screensaver (xscreensaver, actually), by running
a program. I know how to configure the desktop to disable it, but I was hopping not having to do it.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
AFAIK (was looking for this a while ago, to avoid to have daughter to switch of screensaver before starting a game, found nothing) not directly possible through some option. You could think of starting the game through a bash script that stops the screensaver on startup, then starts the game and on exit restarts the screensaver. Or something like that.
On 2013-12-22 15:56, Knurpht wrote:
>
> AFAIK (was looking for this a while ago, to avoid to have daughter to
> switch of screensaver before starting a game, found nothing) not
> directly possible through some option. You could think of starting the
> game through a bash script that stops the screensaver on startup, then
> starts the game and on exit restarts the screensaver. Or something like
> that.
Mmm… yes, I could kill xscreensaver, start game, start xscreensaver.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
Am 22.12.2013 18:33, schrieb Carlos E. R.:
> Interesting.
> But it does not work…
>
Is it really the screensafer? Maybe you also need to disable powersafe
“xset -dpms” in addition.
–
PC: oS 13.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.11 | GTX 650 Ti
ThinkPad E320: oS 13.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.11 | HD 3000
HTPC: oS 13.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.10 | HD 2500
On 2013-12-22 18:33, Carlos E. R. wrote:
> On 2013-12-22 16:35, Martin Helm wrote:
>> What about just editing the .desktop entry if one exists and add the
>> xset commands
>>
>> xset s off; [original entry]; xset s on
>>
>
> Interesting.
> But it does not work…
No, it does not work. In order to verify that the game was not interfering, I tried on a terminal,
did the xset thing, and waited. When I came back, the screensaver was running.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
On 2013-12-22 18:59, Martin Helm wrote:
> Am 22.12.2013 18:33, schrieb Carlos E. R.:
>> Interesting.
>> But it does not work…
>>
>
> Is it really the screensafer? Maybe you also need to disable powersafe
> “xset -dpms” in addition.
Sure. It is the xscreensaver with the “GLMatrix” program.
I have been also reading the xscreensaver manual. There is a program named “xscreensaver-command”
with this option:
-deactivate
This tells xscreensaver to pretend that there has just been
user activity. This means that if the screensaver is active
(the screen is blanked), then this command will cause the
screen to un-blank as if there had been keyboard or mouse
activity. If the screen is locked, then the password dialog
will pop up first, as usual. If the screen is not blanked,
then this simulated user activity will re-start the count-
down (so, issuing the -deactivate command periodically is
one way to prevent the screen from blanking.)
I might run a loop in a script, with an out condition, calling this every five minutes or so. Or
look in the source code, and create another program that does just that, do whatever it needs every
little while.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
Am 22.12.2013 19:02, schrieb Carlos E. R.:
> No, it does not work. In order to verify that the game was not
> interfering, I tried on a terminal, did the xset thing, and waited. When
> I came back, the screensaver was running.
>
Hmm, starnge that xset does not work, just for fun I made once upon a
time a small script which essentially consists of a while loop which
every 10 seconds moves the mouse by zero pixels (and used it, so i know
it worked)
while :
do
xvkbd -no-keypad -text "\x+0" 2>/dev/null
sleep 10
done
–
PC: oS 13.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.11 | GTX 650 Ti
ThinkPad E320: oS 13.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.11 | HD 3000
HTPC: oS 13.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.10 | HD 2500
Am 22.12.2013 20:55, schrieb Jim Henderson:
> That doesn’t affect xscreensaver, only the dpms screen blanker IIRC.
Thanks Jim, that explains why the xset commands work on my htpc to avoid
blanking with gnome 3, gnome simply does not use xscreensaver, I forgot
that and expected them to work in other desktop environments.
–
PC: oS 13.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.11 | GTX 650 Ti
ThinkPad E320: oS 13.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.11 | HD 3000
HTPC: oS 13.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.10 | HD 2500
