[schapplm]

After my update from Helix to Isengard, my LIRC remote stops working after about one minute in linux standalone mode with the Kodi window manager. Before the update, everything was fine. The problem does not occur in regular starting mode (non-standalone).

In standalone mode (any of the two "kodi" window managers in the login screen selected), I start pressing remote keys directly after startup, which works until some point. then I continue pressing the buttons without any effect

21:03:20 T:140453970741184 DEBUG: Keyboard: scancode: 0x72, sym: 0x0113, unicode: 0x0000, modifier: 0x0
21:03:20 T:140453970741184 DEBUG: OnKey: right (0xf083) pressed, action is Right
21:03:20 T:140453970741184 DEBUG: LIRC: Update - NEW at 20563:6a 0 KEY_RIGHT /dev/input/event2 (KEY_RIGHT)
21:03:32 T:140452644763392 DEBUG: Thread JobWorker 140452644763392 terminating (autodelete)
21:03:33 T:140452894230272 DEBUG: Thread JobWorker 140452894230272 terminating (autodelete)
21:03:33 T:140452669941504 DEBUG: Thread JobWorker 140452669941504 terminating (autodelete)
21:03:34 T:140453970741184 DEBUG: SECTION:UnloadDelayed(DLL: special://xbmcbin/system/ImageLib-x86_64-linux.so)
21:03:34 T:140453970741184 DEBUG: Unloading: /ImageLib-x86_64-linux.so

Starting from the normal Ubuntu window manager unity in either fullscreen ("kodi -fs") or standalone mode ("kodi --standalone"), I get a different line for the remote key action and can continue after the unloading of the .so file:

21:06:06 T:139825728063424 DEBUG: OnKey: 169 (0xa9) pressed, action is Left
21:06:06 T:139825728063424 DEBUG: LIRC: Update - NEW at 9461:00000014f21d0000 00 KEY_LEFT x10_medion (KEY_LEFT)
21:06:06 T:139825728063424 DEBUG: OnKey: 169 (0xa9) pressed, action is Left
21:06:08 T:139825728063424 DEBUG: ------ Window Init (Pointer.xml) ------
21:06:13 T:139825728063424 DEBUG: ------ Window Deinit (Pointer.xml) ------
21:06:28 T:139824405149440 DEBUG: Thread JobWorker 139824405149440 terminating (autodelete)
21:06:28 T:139824648406784 DEBUG: Thread JobWorker 139824648406784 terminating (autodelete)
21:06:28 T:139823876638464 DEBUG: Thread JobWorker 139823876638464 terminating (autodelete)
21:06:30 T:139825728063424 DEBUG: SECTION:UnloadDelayed(DLL: special://xbmcbin/system/ImageLib-x86_64-linux.so)
21:06:30 T:139825728063424 DEBUG: Unloading: /ImageLib-x86_64-linux.so
21:07:47 T:139825728063424 DEBUG: LIRC: Update - NEW at 110464:00000014749f0000 00 KEY_RIGHT x10_medion (KEY_RIGHT)
21:07:47 T:139825728063424 DEBUG: OnKey: 168 (0xa8) pressed, action is Right

My setup is Ubuntu 14.04, Kodi 15.0 Isengard, Medion x10 remote configured with LIRC, lircmap.xml and keyboard.xml according to this (german) guide.

I have another Streacom IR remote control on the same machine configured according to this post, which is still working, after the x10 remote stops working. Since this remote is mapped as a HID, this should not influence the LIRC behavior.

Has something changed regarding the remote control handling in version 15 Isengard? I don't want to roll back the update because of this.

[schapplm]

I tried a few solutions to solve this and found out, that the issue is the starting time of kodi after system boot.
If started immediately after booting, the LIRC implementation in kodi is somehow not able to get the correct deviceName: "/dev/input/event3" instead of "x10_medion".
Therefore the whole LIRCMap does not work since the remote name is used there.
There is no difference between standalone mode without window manager or with Ubuntu Gnome window manager.
The LIRC daemon works normally though:

Code:

$irw
00000014749f0000 00 KEY_RIGHT x10_medion

If I add a time delay long enough to the kodi shell script, the remote works (sleep 10 was not enough):
/usr/bin/kodi-standalone

Code:

sleep 25
APP=Kodi
...

My guess is, that Kodi starts, before the LIRC daemon is started and restarted properly.

Further Debug Info: To fix some lirc bug, I use:
/etc/rc.local

Code:

/etc/init.d/lirc restart

After reinstalling LIRC I could not reproduce the remote working in standalone mode and then stopping to work after a few seconds.

I tried the same configuration (settings, remote control, Ubuntu and Kodi versions) on another (slower) machine and the error did not occur, so it could be tricky to find.