[mythtv-users] Remote control issue after Ubuntu upgrade

[Allen Edwards]

On Thu, Oct 4, 2018 at 6:42 AM Jerry <mythtv at hambone.e4ward.com> wrote:

> On Thu, Oct 4, 2018 at 6:11 AM Phill Edwards <philledwards at gmail.com>
> wrote:
>
>> I know lots of people have been having remote control problems after
>> upgrading to 18.04 and I'm yet another one. But I think I'm very close.
>>
>> I use a Harmony universal remote which worked fine on my 16.04 Ubuntu
>> frontend. I had it set up with devinput so I didn't need to run lirc .
>> After upgrading to Ubuntu 18.04 the only buttons that generate a response
>> in MythTV are up, down, left, and right.
>>
>> When I run ir-keytable I get a list of mappings as per below, and when I
>> run ir-keytable -t in a terminal window I get key responses.
>>
>> ~$ sudo ir-keytable --read --device=/dev/input/event4
>> scancode 0x800f0400 = KEY_NUMERIC_0 (0x200)
>> scancode 0x800f0401 = KEY_NUMERIC_1 (0x201)
>> scancode 0x800f0402 = KEY_NUMERIC_2 (0x202)
>> scancode 0x800f0403 = KEY_NUMERIC_3 (0x203)
>> scancode 0x800f0404 = KEY_NUMERIC_4 (0x204)
>> scancode 0x800f0405 = KEY_NUMERIC_5 (0x205)
>> scancode 0x800f0406 = KEY_NUMERIC_6 (0x206)
>> scancode 0x800f0407 = KEY_NUMERIC_7 (0x207)
>> scancode 0x800f0408 = KEY_NUMERIC_8 (0x208)
>> scancode 0x800f0409 = KEY_NUMERIC_9 (0x209)
>> scancode 0x800f040a = KEY_DELETE (0x6f)
>> scancode 0x800f040b = KEY_ENTER (0x1c)
>> scancode 0x800f040c = KEY_SLEEP (0x8e)
>> scancode 0x800f040d = KEY_MEDIA (0xe2)
>> scancode 0x800f040e = KEY_MUTE (0x71)
>> scancode 0x800f040f = KEY_INFO (0x166)
>> scancode 0x800f0410 = KEY_VOLUMEUP (0x73)
>> scancode 0x800f0411 = KEY_VOLUMEDOWN (0x72)
>> scancode 0x800f0412 = KEY_CHANNELUP (0x192)
>> scancode 0x800f0413 = KEY_CHANNELDOWN (0x193)
>> scancode 0x800f0414 = KEY_FASTFORWARD (0xd0)
>> scancode 0x800f0415 = KEY_REWIND (0xa8)
>> scancode 0x800f0416 = KEY_PLAY (0xcf)
>> scancode 0x800f0417 = KEY_RECORD (0xa7)
>> scancode 0x800f0418 = KEY_PAUSE (0x77)
>>
>> And my $HOME/.mythtv/lircrc looks like this:
>> ...
>> begin
>>     remote = devinput
>>     prog = mythtv
>>     button = KEY_NUMERIC_1
>>     config = 1
>>     repeat = 0
>>     delay = 10
>> end
>>
>> begin
>>     remote = devinput
>>     prog = mythtv
>>     button = KEY_NUMERIC_0
>>     config = 0
>>     repeat = 0
>>     delay = 10
>> end
>> ...etc...
>>
>> So devinput is getting the button presses and they're being mapped to
>> keys like KEY_NUMERIC_0, KEY_PAUSE etc but MythTv frontend doesn't seem to
>> be registering these button presses. So what have I omitted that will fill
>> in the final piece of the jigsaw and get MythTV to respond? Is there
>> another config file somewhere I have to modify?
>>
>> I don't know if this is your fix but I would look at your
> lirc_options.conf.  In my Fedora system, it's located at
> /etc/lirc/lirc_options.conf
>
> It could be that your driver line says "driver = default" (or possibly
> something else?) instead of "driver = devinput".  If that's the case, lircd
> won't listen to devinput.
>
> Test with irw as well.  Also make sure that the name of your remote
> (mceusb, myremote or similar) is correct.  In my system, the remote
> configuration files are in /etc/lirc/lircd.conf.d  I thought there was a
> reference to it in ~/.lircrc (or wherever your file is) but I don't see it
> there.  LIRC confuses me a lot and I haven't tweaked my setttings in over a
> year.  Still, that might be important also.
>
> I may be wrong but it's worth a try.  A few upgrades ago, that driver
> setting was flipped on me (in the other direction).  It could be that a
> package upgrade changed that setting for you.
>
> Hopefully a LIRC guru will chime in and give your some proper help.
>

I don't know myself but I did get the following reply when setting up my
remote on a new 16.04 install.

lirc in 16.04 is a quite old version (0.9.0).  The version in 18.04 is
0.10.0, and its Python configuration tools are badly broken - clearly
no one ever tested them.  They can not find their libraries and crash
when run.  I believe lircd itself is fine, and if the config files can
be manually created it will work.  And it is rather more capable than
0.9.0.  But I have not actually verified that as I have not upgraded
any of my running systems to 18.04.1 yet.

So your choice of 16.04 is fortuitous - you need a working lirc, and
18.04 does not have one yet.

Also, there is another post this morning dealing with remotes that might be
along the same track.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20181004/ab2278d4/attachment.html>