2017-01-29, 23:59
This has been baffling me for a while. I have a Linux box running Kodi 16.1 and a Imon HD VFD/IR receiver.
Everything ran beautifully until i updated to the 16.x line. I use an iMon Pad remtoe (http://www.origenae.co.kr/images/product...d_shot.jpg) and now, when i press certain buttons Kodi crashes, freezing its display and accepting no further input. The rest of the system is responsive though, but the only solution is to restart the box.
The only buttons which seem to work on the remote are the directional arrows and the "Enter" button. Everything else just kills Kodi unceremoniously, even with debugging logs enabled:
I've spent some time double checking my configs and keymaps (have none on ~/.kodi/userdata/keymaps), but i'm unable to trace this issue down. Any idea what might be going on here?
Regards.
Code:
22:45:43 T:140259685433728 NOTICE: special://profile/ is mapped to: special://masterprofile/
22:45:43 T:140259685433728 NOTICE: -----------------------------------------------------------------------
22:45:43 T:140259685433728 NOTICE: Starting Kodi (16.1 Git:Unknown). Platform: Linux x86 64-bit
22:45:43 T:140259685433728 NOTICE: Using Release Kodi x64 build
22:45:43 T:140259685433728 NOTICE: Kodi compiled Jan 22 2017 by GCC 6.3.1 for Linux x86 64-bit version 4.7.0 (263936)
22:45:43 T:140259685433728 NOTICE: Running on Arch Linux rolling, kernel: Linux x86 64-bit version 4.9.6-1-ARCH
22:45:43 T:140259685433728 NOTICE: FFmpeg statically linked, version: 2.8.6-kodi-2.8.6-Jarvis-16.0
22:45:43 T:140259685433728 NOTICE: Host CPU: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz, 4 cores available
22:45:43 T:140259685433728 NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
22:45:43 T:140259685433728 NOTICE: special://xbmcbin/ is mapped to: /usr/lib/kodi
22:45:43 T:140259685433728 NOTICE: special://masterprofile/ is mapped to: /home/kodi/.kodi/userdata
22:45:43 T:140259685433728 NOTICE: special://home/ is mapped to: /home/kodi/.kodi
22:45:43 T:140259685433728 NOTICE: special://temp/ is mapped to: /home/kodi/.kodi/temp
22:45:43 T:140259685433728 NOTICE: The executable running is: /usr/lib/kodi/kodi.bin
22:45:43 T:140259685433728 NOTICE: Local hostname: xxxxxxxxxx
22:45:43 T:140259685433728 NOTICE: Log File is located: /home/kodi/.kodi/temp/kodi.log
22:45:43 T:140259685433728 NOTICE: -----------------------------------------------------------------------Everything ran beautifully until i updated to the 16.x line. I use an iMon Pad remtoe (http://www.origenae.co.kr/images/product...d_shot.jpg) and now, when i press certain buttons Kodi crashes, freezing its display and accepting no further input. The rest of the system is responsive though, but the only solution is to restart the box.
The only buttons which seem to work on the remote are the directional arrows and the "Enter" button. Everything else just kills Kodi unceremoniously, even with debugging logs enabled:
Code:
...
22:36:23 T:140601076740480 DEBUG: OnKey: left (0xf082) pressed, action is Left
22:36:24 T:140601076740480 DEBUG: Keyboard: scancode: 0x72, sym: 0x0113, unicode: 0x0000, modifier: 0x0
22:36:24 T:140601076740480 DEBUG: OnKey: right (0xf083) pressed, action is Right
22:36:24 T:140601076740480 DEBUG: Keyboard: scancode: 0x72, sym: 0x0113, unicode: 0x0000, modifier: 0x0
22:36:24 T:140601076740480 DEBUG: OnKey: right (0xf083) pressed, action is Right
22:36:25 T:140601076740480 DEBUG: Keyboard: scancode: 0x72, sym: 0x0113, unicode: 0x0000, modifier: 0x0
22:36:25 T:140601076740480 DEBUG: OnKey: right (0xf083) pressed, action is Right
22:36:25 T:140601076740480 DEBUG: Keyboard: scancode: 0x72, sym: 0x0113, unicode: 0x0000, modifier: 0x0
22:36:25 T:140601076740480 DEBUG: OnKey: right (0xf083) pressed, action is Right
22:36:26 T:140601076740480 DEBUG: Keyboard: scancode: 0x72, sym: 0x0113, unicode: 0x0000, modifier: 0x0
22:36:26 T:140601076740480 DEBUG: OnKey: right (0xf083) pressed, action is Right
* A BUTTON IS PRESSED HERE - Kodi freezes *I've spent some time double checking my configs and keymaps (have none on ~/.kodi/userdata/keymaps), but i'm unable to trace this issue down. Any idea what might be going on here?
Regards.
