By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,529 Members | 946 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,529 IT Pros & Developers. It's quick & easy.

How to stop screensaver from starting up

P: n/a
Hello everyone,

does anyone know a way to stop the screensaver under linux from
starting up while a certain process is running?
I need this because I experience a memory leak while recording
wav-files every time the screensaver starts.
It is a Tkinter application, btw.
Any help would be very appreciated.


Jul 18 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Jeff Epler <je****> wrote in message news:<ma**********************************@python. org>...

Thanks for the feedback,
For systems using xscreensaver, see xscreensaver-command(1).

You could use
xscreensaver-command -throttle
to force screen blanking (not screensaver) when the system is idle
xscreensaver-command -exit
to force the screensaver process to exit. In the former case, you would
xscreensaver-command -unthrottle
to restart the screensaver, and in the latter case
xscreensaver -nosplash
in the latter.

This is not robust if multiple processes all try to manipulate the
screensaver without some additional kind of locking.


I know this, but what I had in mind was, if there is a way to disable
the screensaver directly from within python/tkinter while a certain
process inside my application is running (it is the recording issue I
have posted here a while ago, where it seems like memory leaks occur
while recording when a screensaver starts up).
The basic problem with the xscreensaver command is of course that it
will not work if kde-screensavers are used.
I am sorry if this is a silly question, I just thought it might be
easier to disable the screensaver while recording than to try a
workaround for the snack recording function; maybe what I want is
simply not possible.

Best regards

Jul 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.