<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="font-family: Verdana; font-size: 13px; "><font color="#660066"></font><blockquote type="cite"><font color="#660066">>> about 30% of the time, the graphics card wont wake up to a remote <br>>> control press. Plugging in a mouse and wiggling it wakes it up. BUT, <br>>> mythfrontend is completely unresponsive. I always leave myth on the <br>>> Watch Recordings page, and when this happens, the frontend is frozen <br>>> on that page, but completely empty with no recordings listed. <br></font><br>I seem to recall another post about the frontend locking up if it sits <br>at the watch recording screen for a long time, though I don't think a <br>solution was ever mentioned. <br><br>Try leaving it on a screen other than watch recordings and see if it <br>freezes (try the main menu and the guide grid). Assuming it's only on <br>that screen, it could be a number of different things. I'd try <br>disabling the live preview if you have it enabled, as there may be a <br>bug in that code. I fixed a bug with the live preview locking up the <br>watch recording screen, but maybe there's still another part of it I <br>didn't catch. <br><br>It also may be possible that the watch recording screen is opening a <br>DB connection and then just continues to reuse it, and after a while <br>the handle becomes stale. I know this type of thing happens when I <br>connect from my work computer to my home computer. The firewall does <br>NAT, and when it stops seeing traffic on a port for about 30 minutes, <br>it just forgets about the connection. The socket never actually <br>disconnects...just disappears. Now, you wouldn't likely be doing NAT <br>on your internal network, but maybe there are other configurations <br>that do similar things (maybe a software firewall?). <br><br><br>-- <br>Ron </blockquote><br></span><div><font class="Apple-style-span" face="Verdana" size="3"><span class="Apple-style-span" style="font-size: 13px;">In my extremely limited testing, it appear that leaving it idle on the main menu instead of the recordings list prevents it from freezing. Regarding network/NAT issues, I'm using a frontend/backend so it should only be connecting locally.</span></font></div><div><font class="Apple-style-span" face="Verdana" size="3"><span class="Apple-style-span" style="font-size: 13px;"><br></span></font></div><div><font class="Apple-style-span" face="Verdana" size="3"><span class="Apple-style-span" style="font-size: 13px;">So is this a common issue, or is it something in my setup? Seems like a pretty major bug. Reportable?</span></font></div><div><font class="Apple-style-span" face="Verdana" size="3"><span class="Apple-style-span" style="font-size: 13px;"><br></span></font></div><div><font class="Apple-style-span" face="Verdana" size="3"><span class="Apple-style-span" style="font-size: 13px;">Thanks</span></font></div></body></html>