<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;"><br>
Has anyone had any luck in resolving this yet? I just had a forced<br>
machine upgrade (motherboard failure), and am seeing this issue, and<br>
because so much has changed (new motherboard, video card, fresh OS and<br>
Myth installation) I can't isolate the exact change that caused it.<br>
My symptoms sound similar -- every so often (usually a couple times an<br>
hour at least), there's no response for several minutes to any remote<br>
commands. The light on the original MCE USB receiver flashes, and<br>
"irw" shows the button presses, so it appears that lirc is receiving<br>
the IR commands properly. Eventually, Myth responds to some of the<br>
old commands. This really sounds like a mythfrontend issue to me, but<br>
I don't know how to<br>
<br>
Hardware: Pentium 4 630 (2.8Ghz), Gigabyte GA-EG31M-S2 motherboard,<br>
original MS MCE USB receiver (but using the Philips 1181 IR codes).<br>
<br>
OS: Fedora 9, kernel 2.6.26.6-79.fc9.i686<br>
<br>
mythfrontend --version: (latest 0.21-fixes from ATRPMS)<br>
Please include all output in bug reports.<br>
MythTV Version : 18753M<br>
MythTV Branch : branches/release-0-21-fixes<br>
Library API : 0.21.20080304-1<br>
Network Protocol : 40<br>
Options compiled in:<br>
linux release using_oss using_alsa using_arts using_jack<br>
using_backend using_dbox2 using_dvb using_firewire using_frontend<br>
using_hdhomerun using_iptv using_ivtv using_joystick_menu<br>
using_libfftw3 using_lirc using_opengl_vsync using_opengl_video<br>
using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmcw<br>
using_xvmc_vld using_glx_proc_addr_arb using_bindings_perl<br>
using_bindings_python using_opengl using_ffmpeg_threads<br>
using_libavc_5_3 using_live<br>
<br>
hwclk --debug reports no errors.<br>
<br>
This is a severe WAF hindrance, to say the least :-)<br>
<br>
I'm going to try tonight to install from the older RPMs I had on the<br>
previous system's HD partition and see if I can better isolate, but<br>
I'm not confident in that and was hoping someone had figured out the<br>
cause.<br>
</blockquote></div><br>I am still seeing this same behavior with similar hardware and a similar remote. I haven't been able to figure it out, either. I would love to find the cause.<br>