NUC10 + LE13 Nightly Generic - IR Remote not working

    nightly-20240613-18becd8 - remote is not working with this one (no reaction to any button)

    nightly-20240612-1a71ae6 - remote is back to normal

    Perhaps this is the reason:

    Code
    Jun 15 00:10:24.294870 NUC-ELEC eventlircd[541]: Assertion 'udev_device && key' failed at src/libudev/libudev-device.c:194, function udev_device_get_property_value(). Aborting.
Jun 15 00:10:24.329341 NUC-ELEC systemd[1]: eventlircd.service: Main process exited, code=dumped, status=6/ABRT
Jun 15 00:10:24.329360 NUC-ELEC systemd[1]: eventlircd.service: Failed with result 'core-dump'.

    On my RPI 4B the IR Remote also stopped working after upgrade to LibreELEC-RPi4.aarch64-13.0-nightly-20240614-18becd8

    Analyzed the issue a bit and it looks ir-keytable does not see the rc0 device anymore but rc1 instead in my case.

    ls /dev/lirc*
    /dev/lirc0 /dev/lirc1 /dev/lirc2

    ir-keytable

    Found /sys/class/rc/rc1/ with:
    Name: gpio_ir_recv
    Driver: gpio_ir_recv
    Default keymap: rc-rc6-mce
    Input device: /dev/input/event3
    LIRC device: /dev/lirc1
    Attached BPF protocols:
    Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm
    Enabled kernel protocols: lirc nec
    bus: 25, vendor/product: 0001:0001, version: 0x0100
    Repeat delay: 500 ms, repeat period: 125 ms
    Found /sys/class/rc/rc2/ with:
    Name: MyGica Mini DVB-(T/T2/C) USB Stick T230C
    Driver: dvb_usb_dvbsky
    Default keymap: rc-total-media-in-hand-02
    Input device: /dev/input/event4
    LIRC device: /dev/lirc2
    Supported kernel protocols: rc-5
    Enabled kernel protocols: rc-5
    bus: 3, vendor/product: 0572:c689, version: 0x0800
    Repeat delay: 500 ms, repeat period: 125 ms


    As the default device is still /dev/lirc0, then some commands like irw does not work.

    cat /etc/lirc/lirc_options.conf
    # These are the default options to lircd, if installed as
    # /etc/lirc/lirc_options.conf. See the lircd(8) and lircmd(8)
    # manpages for info on the different options.
    #
    # Some tools including mode2 and irw uses values such as
    # driver, device, plugindir and loglevel as fallback values
    # in not defined elsewhere.

    [lircd]
    nodaemon = False
    driver = default
    device = /dev/lirc0
    output = /run/lirc/lircd.socket
    pidfile = /run/lirc/lircd.pid
    plugindir = /usr/lib/lirc/plugins
    permission = 666
    allow-simulate = No
    repeat-max = 600
    #effective-user =
    #listen = [address:]port
    #connect = host[:port]
    #loglevel = 6
    #release = true
    #release_suffix = _EVUP

    #logfile = ...

    [lircmd]
    uinput = False
    nodaemon = False

    # modinit is not supported in LibreELEC

    # [modinit]
    # code = /usr/sbin/modprobe lirc_serial
    # code1 = /usr/bin/setfacl -m g:lirc:rw /dev/uinput
    # code2 = ...

    irw
    Cannot connect to socket /run/lirc/lircd: Connection refused


    The /etc/lirc/lirc_options.conf file is read only and currently I don't know how to easily change the device configuration to /dev/lirc1 as the shadow file in /storage/.config/ folder did not help.

    But maybe it's a wrong way anyway...

    Can someone please trigger nightly build for x86 as well?

    btw. I always had impression that nightlies are triggered via some automation if at least one PR is merged during a day? But it seems that they are triggered somehow randomly, otherwise we should see 5 builds during June 11-15 and this would be consistent for all device types:

    In the ideal world all our PR's compile without issues, all the dependant services have 100% uptime, and all the build servers have infinite disk space. Reality is often different.