On Friday 20 March 2015 11:31:12 Gene Heskett wrote:
> I recall I had a heck of a time in the past with the older kde, in
> keeping the monitors/screensaver set so it might show a few minutes of
> the screensaver of choice, and to powerdown the monitor after a few
> minutes of screen saver.  But it can't remember those settings more
> than a week or so, so I just put a couple entries in my crontab:
>
> */1 * * * * * xset +dpms
> */1 * * * * * xset dpms 300 0 600

Actually this is wrong as it then is effectively  * * * * * *, the star 
string s/b * */1 * * * * as it was doing it on the minute, but then cron 
was emailing me that it could not open display "", so I have now made it 
hourly, and added -display 0:0 after the xset to see if that works...

Gotta be a way to make this work. I would have and had always assumed 
that doing something from the crontab was exactly like my typing it into 
a terminal, so whats the deal with that?  Why can't my crontab do 
anything I can type?

> To see if refreshing its memory hourly will effect a fix.
>
> But it sure would be nice if we didn't have to overpower it like that
> to keep it working.
>
> In TDE control center, its set 5,0,10 but that seems not to affect it,
> when it has failed the pheripherals/display/screensaver and display
> power management are all zeroed out or the checkboxes cleared.
> It appears is as if a zmalloc has gone astray?
> Under appearance/screensaver its set to start a slide show after 4
> minutes.  The memory of whatever it uses for the "elevator music for
> the eyeball" also seems transient, it switches to either a blank
> screen or some glx thing that burns up the cpu, again at random
> intervals that do not seem to correlate with the dpms settings
> failures.
>
> Info, bug action, your pick. ;-)
>
> Cheers, Gene Heskett

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>