On Wed, Jan 14, 2009 at 6:04 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 01/14/2009 02:28 PM, Darren Hart wrote:<br>
> I've just updated to 19626 and disabled gnome-screensaver. I watched<br>
> two hours of HD recordings and had no remote lag. So far so good.<br>
> I'll report back if it resurfaces.<br>
<br>
</div>Thanks for the feedback. Out of curiosity, did you try running with<br>
r19626 with gnome-screensaver enabled (you'll also need to restart the<br>
frontend after restarting gnome-screenaver)? Once past r19222, you<br>
shouldn't see any lag--it only runs gnome-screensaver-command at most<br>
once every 30 seconds.<br>
<br>
If that's not the case, please let me know as it means that<br>
gnome-screensaver-command is, er, not cooperating, and we need to do<br>
something about it.<br></blockquote></div><br>I am currently running build 19626 with gnome screen-saver and things seem to be better, but I haven't used it enough since the update to be sure. There have been a few times of nonresponsiveness but I think it was during high cpu usage moments. Before I was using build 19536 (I think) and there was a lag of like 30 seconds every time I started mythfrontend. The keyboard would work but not the remote. There still seems to be a lag at start up in this build but it isn't nearly as long. <br>