Announcement

**ronw** · Jan 07, 2012, 07:56 PM

Re: xset's dpms settings change on their own

I thought this was a 4.8 beta issue, but maybe not.

If you change the Dim Display and Screen Energy Savings settings in System Settings > Power Management, you can run xset q and see the DPMS stuff changing. I turned both settings off in Power Management, applied, turned both back on, applied, and turned them off again. DPMS is now saying it is disabled. Not sure if it will stick after a logout.

**schnelle** · Jan 07, 2012, 09:35 PM

Re: xset's dpms settings change on their own

Originally posted by ronw

I turned both settings off in Power Management, applied, turned both back on, applied, and turned them off again. DPMS is now saying it is disabled. Not sure if it will stick after a logout.

This is the method I use to fix it too

**DoYouKubuntu** · Jan 07, 2012, 10:56 PM

Re: xset's dpms settings change on their own

Originally posted by ronw

I thought this was a 4.8 beta issue, but maybe not.

If you change the Dim Display and Screen Energy Savings settings in System Settings > Power Management, you can run xset q and see the DPMS stuff changing. I turned both settings off in Power Management, applied, turned both back on, applied, and turned them off again. DPMS is now saying it is disabled. Not sure if it will stick after a logout.

I figured I'd give it a try, so I've done what you said and will now wait to see if it changes on its own again. Note that, for me, it had nothing to do with logging in and out--it would change on its own without having logged out and back in--so that test isn't really relevant in my case.

**de_koraco** · Jan 08, 2012, 03:49 AM

Re: xset's dpms settings change on their own

Add this to xorg.conf or xorg.conf.d/20-serverflags.conf

Code:

Section "ServerFlags"
    Option   "blank time" "0"
    Option   "standby time" "0"
    Option   "suspend time" "0"
    Option   "off time" "0"
    Option   "dpms" "false"
EndSection

**DoYouKubuntu** · Jan 08, 2012, 10:50 AM

Re: xset's dpms settings change on their own

Originally posted by de_koraco

Add this to xorg.conf or xorg.conf.d/20-serverflags.conf

Code:

Section "ServerFlags"
    Option   "blank time" "0"
    Option   "standby time" "0"
    Option   "suspend time" "0"
    Option   "off time" "0"
    Option   "dpms" "false"
EndSection

I'm confused.

Since I'm already using xset -dpms in my /etc/rc.local file, I didn't think doing anything via an xorg.conf file was necessary. Plus, as I said in my OP, the only one I have is just a sample, located in /usr/share/doc/xserver-xorg-video-nouveau/examples/xorg.conf

**OneLine** · Jan 08, 2012, 11:54 AM

Re: xset's dpms settings change on their own

Here the Xset seems to work as expected.

I'm using it through the On/Off switch plasmoid.

[img width=400 height=262]http://img6.imageshack.us/img6/9002/screen20120108194146.png[/img]

The On command "xset dpms force on && xset -dpms" is executed on startup.

There is a bug report: Laptop only remains DPMS off for 2 seconds / https://bugs.launchpad.net/ubuntu/+s...er/+bug/447728

An alternative way to disable the xset

The xset is part of the x11-xserver-utils:

Code:

Description: X server utilities
 An X client is a program that interfaces with an X server (almost always via
 the X libraries), and thus with some input and output hardware like a
 graphics card, monitor, keyboard, and pointing device (such as a mouse).
 .
 This package provides a miscellaneous assortment of X Server utilities
 that ship with the X Window System, including:
 - iceauth, a tool for manipulating ICE protocol authorization records;
 - rgb;
 - sessreg, a simple program for managing utmp/wtmp entries;
 - xcmsdb, a device color characteristic utility for the X Color Management
  System;
 - xgamma, a tool for querying and setting a monitor's gamma correction;
 - xhost, a very dangerous program that you should never use;
 - xmodmap, a utility for modifying keymaps and pointer button mappings in X;
 - xrandr, a command-line interface to the RandR extension;
 - xrdb, a tool to manage the X server resource database;
 - xrefresh, a tool that forces a redraw of the X screen;
 - xset, a tool for setting miscellaneous X server parameters;
 - xsetmode and xsetpointer, tools for handling X Input devices;
 - xsetroot, a tool for tailoring the appearance of the root window;
 - xstdcmap, a utility to selectively define standard colormap properties;
 - xvidtune, a tool for customizing X server modelines for your monitor.

The Xset executable is: /usr/bin/xset. The renaming ( /removing) of it should disable it permanently

**de_koraco** · Jan 08, 2012, 01:32 PM

Re: xset's dpms settings change on their own

Originally posted by DoYouKubuntu

I'm confused.

Since I'm already using xset -dpms in my /etc/rc.local file,

Maybe you should use it in KDEs autostart settings (is there such a thing?), as doing it in /etc/rc.local might be invalidated given that X expects user session stuff to be controlled in user sessions. Just an idea really, who knows what X has in mind.

As for .xorg.conf, if you don't have that file, you're using a free GPU driver. So we're not gonna make the traditional /etc/X11/xorg.conf, but just apply DPMS settings in the xorg.conf.d directory. Make a file called 20-dpms.conf in /etc/X11/xorg.conf.d and paste the stuff I gave you in the earlier post if you can't implement xset -dpms via KDE.

**DoYouKubuntu** · Jan 08, 2012, 02:53 PM

Re: xset's dpms settings change on their own

Thanks, guys. Here's an update: After doing what ronw suggested, so far so good!

I've even shutdown the laptop and immediately after booting back up checked xset q and DPMS was still disabled. I don't know yet if it's going to last, but if it doesn't I'll try the other suggestions.

**kubicle** · Jan 08, 2012, 03:11 PM

Re: xset's dpms settings change on their own

Originally posted by DoYouKubuntu

I'm confused.

Since I'm already using xset -dpms in my /etc/rc.local file

There are a few issues (that come to mind) with trying to run xset from rc.local:
1. DISPLAY variable is likely not set for rc.local, so you'd have to use something like:

Code:

DISPLAY=:0 xset -dpms

2. It's possible that rc.local runs prior to X initialization, and the xset has no effect.

Disabling dpms in xorg configs (or other X initialization files) or with kde startup (if you'd wish it to be a per-user setting) is generally a better idea than rc.local.

It's also possible (although I haven't checked) that some power management tools (like laptop-mode-tools or xscreensaver) change the dpms settings per their configuration (if you see that the dpms settings change at runtime)

Announcement

xset's dpms settings change on their own

xset's dpms settings change on their own

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment