NUC+remote power button problems

    I was reluctant to reply seeing the vitriol unleashed in my absence.

    The media remote I am using is a generic USB 2.4ghz one. It doesn't even have a model number it is so generic, and it is detected as a keyboard. I will not be changing the remote as it works perfectly on other LE installs and devices, and as a result I have several. The remote is not the issue.

    This is why in the OP I linked to other threads with users encountering similar bugs caused by LE's handling of keyboard power button presses. OSMC works fine with this remote too across all hardware, so this issue is definitely localised to LE on this NUC.

    As mentioned in the OP, I have tried the methods linked therein.

    If anyone has any ideas that aren't in the threads I linked, please do reply. Let's try and keep it on topic this time; if you have a personal opinion about me that is not relevant to troubleshooting this issue.

    Edited once, last by Wwwr (August 18, 2022 at 7:16 AM).

    Quote from HiassofT

    See here: RE: Remote power off button is different at kodi 17 then at kodi 18 whe using LE

    Your NUC, running X11, works differently than RPi and most likely you are using a remote with a receiver which "looks like" a keyboard to the system. You have to configure systemd to ignore it, otherwise both it and kodi will react to the (sleep?) button. On RPi also keyboard-like devices get grabbed exclusively by kodi so systemd doesn't "see" the button press at all.

    so long,

    Hias

    Please read the OP before replying with an answer.

    LE does not support every piece of hardware on this planet. Apparently, your remote control or infrared receiver is the cause of this issue. I have been using LE with the exact same NUC for years with no problems and use hardware which does work properly.

    Your issue will not fix itself. You can modify the software (LE) for your particular remote and receiver or buy compatible hardware. That's your choice.

    Quote from Wwwr

    Please read the OP before replying with an answer.

    I have read your post and the linked thread, please read my posts as well and try what I suggested.

    First of all the first thread you linked to is rather old, and while systemd-inhibit can still be used it's recommended to configure that via logind.conf.d

    There are actually two different things in play: one thing is system(d) handling of power/sleep/... buttons the second one is how kodi should handle those.

    You need to solve the systemd handling first. stop kodi (systemctl stop kodi), run evtest (from system tools addon) to find out the input device of your remote and then run evtest --grab /dev/input/eventX (replace eventX with the one matching your remote) and press the power button on your remote - this will tell you if it's sending KEY_POWER or KEY_SUSPEND or something else.

    Then setup logind.conf to ignore that key. Reboot, stop kodi again and verify that your system does not power down when you press the button.

    Once you got that working you can start configuring kodi.

    so long,

    Hias

    RPi4 + LE = remote works normally

    NUC + LE = remote issues

    The NUC + LE combo requires a different remote than what you're using because the version of LE used for the NUC is not the same as the version for the RPi4.

    Understand?

    Ask for assistance to modify your version of LE or use a compatible remote.