<div class="gmail_quote">On Mon, Feb 18, 2013 at 7:44 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02/16/2013 03:40 PM, Jerry wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I made another small addition to the wiki: <a href="http://www.mythtv.org/wiki/LIRC#Troubleshooting" target="_blank">http://www.mythtv.org/wiki/<u></u>LIRC#Troubleshooting</a><br>
<br>
It describes how to disable X from listening to your remote if you are using LIRC instead. It threw me for a loop for a little while until I found a solution and I thought others might benefit.<br>
</blockquote>
<br>
Generally most people configure the remote so that it's used only by LIRC, if using LIRC, or only by the kernel, if they really think they don't want LIRC. That may be more appropriate, unless you really want the remote to "work" without LIRC in the text-mode console, but only use LIRC in X. See, for example, <a href="http://www.gossamer-threads.com/lists/mythtv/users/504746#504746" target="_blank">http://www.gossamer-threads.<u></u>com/lists/mythtv/users/504746#<u></u>504746</a><br>
<br></blockquote><div>Thanks, Mike. I think that's a cleaner solution than the one I found. I added the udev rule mentioned in the last post in that thread and all is well.<br> </div></div>