(Solved) How to make xset settings persist in Gnome?

[Dragynn]

Well i've got the stubborn screensaver problem, no way to uninstall them all without taking down Gnome-panel too.  And shutting the gnome screensaver down, apparently activates the xset settings (which I thought was part of xscreensaver?) and it goes blank every ten minutes if i'm not active on it.

 So, opening a terminal and typing:

Code: [Select]

xset s off
xset -dpms will de-activate the dang screen-blanker for the session, my question is, how to make it persist?

Texstar has a script for KDE:
 

Code: [Select]

#!/bin/sh
xset s off
xset -dpms
and that is made an executable .sh file and applied in the appropriate KDE file, but will it work in Gnome? And where would you put it? would you just save the file, and go into "startup applications" and add it there?

[melodie]

Hi,

I just installed xset to Openbox Mini, and there is no such thing as screensaver or xsreensaver in it. Else, last year (2009 version therefore) I succeeded in deativating the screensavers.

Have you given a look at the packages xlockmore, screensaver-settings, and gnome-screensaver ? Are they installed ?

[Dragynn]

Hi,

I just installed xset to Openbox Mini, and there is no such thing as screensaver or xsreensaver in it. Else, last year (2009 version therefore) I succeeded in deativating the screensavers.

Have you given a look at the packages xlockmore, screensaver-settings, and gnome-screensaver ? Are they installed ?

Hi Melodie,

Yep, checked all that, Xlockmore is installed, xscreensaver is not listed as being installed, and Gnome screensaver is installed. With the gnome screensaver and power management daemons DISABLED (not just turned off in the GUI, but stopped from running period (just turning off the screensaver/power management features after you are already booted, does NOT disable the daemons from running), the screen will go blank after 10 minutes if it's not being used and this is xset's doing, because when I disable it manually from terminal, it stops doing it. Here are the settings as of this moment with DPMS and screensaver turned off:

Code: [Select]

[root@localhost bob]# xset -q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000002
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    on     02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  500    repeat rate:  30
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  600
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  65535
Font Path:
  /usr/share/fonts/misc:unscaled,catalogue:/etc/X11/fontpath.d,built-ins
DPMS (Energy Star):
  Standby: 1200    Suspend: 1800    Off: 2400
  DPMS is Disabled
Font cache:
  Server does not have the FontCache Extension
As you can see, there is some sort of screensaver attached to it, and DPMS as well. In the threads I mentioned in my first post, Texstar had included the script he wrote into KDE specifically to fix the problem I am having because it was doing the same thing in KDE.

I know the commands work on xset in Gnome because it is not blanking right now, but after I re-boot it will go back to default settings. So was hoping to get an idea of where and how to apply these commands in Gnome so they will persist.

[Dragynn]

Well that did it sure enough. Copied the script and saved it in my home file just for a first test, the system recognized it with no prompting from me as a script, I opened "startup applications" from the menu and clicked on "Add", and it ran the script on startup, xset DPMS and screensaver is disabled. Probably a better place to put this file, maybe a better way to invoke it, any insights welcome before I mark it solved.

[Xero]

Why not change the default time in the screensaver section that it regards the computer as "idle"?

[melodie]

If I don't want them to start I would remove the most of them... xlockmore and so on... this is still more radical.

[Dragynn]

Why not change the default time in the screensaver section that it regards the computer as "idle"?

Again, let me stress, that I attempted EVERY possible setting in the GUI prior to taking these measures. My ol' eyes may be getting a little fuzzy, but it's still not hard to find the 'Screensaver' and 'Power Management' tabs in the Preferences menu .

To re-state, I wanted to turn the screensaver off, and not HAVE to have two extra processes running at startup, JUST to keep the thing turned OFF. If you disable these two services completely, you are then faced with the xset screensaver and DPMS being ON by default.

To remove either Xlockmore or Gnome screensaver via synaptic, it removes Gnome-panel as well among other things, which I don't want to do as it is part of the heart and soul of the system. I have manually rid myself of most of the Xlockmore stuff, I am more hesitant to start stripping out the Gnome components by hand, if they just stay off and don't take up CPU/RAM and the dang screen-blanker stays disabled, i'll be a happy chappie like Keith

[siamer]

menu -> system -> preferences -> screen saver -> set more thatn 10 min no point to remove that better is just change settings if that will not help than try power manger settings...

good luck
siamer

[Dragynn]

menu -> system -> preferences -> screen saver -> set more thatn 10 min no point to remove that better is just change settings if that will not help than try power manger settings...

good luck
siamer

Hey Siamer,

Don't know how I can make it any clearer that I have already tried all of that and it doesn't work. Tex's workaround however, did the trick