[mythtv-users] screensaver issues

[brad at bradandkim.net]

> I believe MythTV is only designed to work with xscreensaver.  For me
> it just simply works.  Here's what I did.
>
> I'm using fluxbox as a window manager.  I have the following in my
> /home/mythtv/.fluxbox/startup:
>
> [ -x /usr/bin/nvidia-settings ] && /usr/bin/nvidia-settings -l
> /usr/bin/xset s noblank
> /usr/bin/xset s off
> /usr/bin/xset -dpms
> numlockx
> /usr/bin/fluxbox &
> /usr/bin/xscreensaver -no-splash &
> sleep 2
> exec /usr/bin/mythfrontend -l /var/log/mythtv/mythfrontend.log -v
> important,general
>
> The xset commands disable DPMS.  Note that after I start xscreensaver
> in the background, I have a 'sleep 2'.  I have the frontend login
> session set to respawn in inittab.  I found that when I quit the
> frontend and it respawned, it had a tendency to start the frontend
> much faster than it does on initial bootup, and without that sleep
> command it often started before xscreensaver was truly ready.  The
> sleep command fixed that by always giving xscreensaver a chance to
> start.
>
> Using either the remote or the keyboard stops any active screen saver
> and does reset the inactivity timeout.  I have mine set to three
> minutes.
>
> It works great.  I have a RPCRT TV, and I really didn't want to risk
> burn-in.
>
> Tom

Thanks Tom.  I will give this method a try as soon as I get a chance.  It
is possible that mythfrontend is starting before xscreensaver and that
might be my issue.

Thanks,

Brad