Posts by ghtester

    I have encountered in latest LE 13 Nightly on RPi 4B ( LibreELEC-RPi4.aarch64-13.0-nightly-20241101-5b3a206 ) the KEY_SUBTITLE devinput action in Kodi was changed, when watching the Live TV or video recordings.

    In past it was simply toggling on/off the subtitles, now the subtitle configuration menu is open and the selection must be made. This is very annoying.

    Probably it's a change in Kodi (Build 22.0-ALPHA1 21.90.700). If anybody has a comment related to this change, I would be glad to be informed.

    Currently I don't have a registration in Kodi forum, also for the case it should be related to LE instead, I am opening this thread here.

    I can fix that by remapping the IR Remote key to keyboard's "t" button ( kodi-send --button="t") but I believe this recent KEY_SUBTITLE behavior change is a nonsense...

    So if anyone of developers could revert it back somehow, please do it, I am sure it would be a best solution.

    irw output: 172 0 KEY_SUBTITLE devinput

    Now points to: DialogSelectSubtitle (description: Open a window dialog to select a subtitle stream. (v22 Piers addition))

    In past it was probably pointing to: ShowSubtitles (description: Toggles whether subtitles are shown or not.)

    Another option which would make sense: NextSubtitle (description: Change to the next subtitle language, if there is more than one.)


    It's at line 201 of the /usr/share/kodi/system/keymaps/remote.xml file.

    The quick fix is to copy that file to /storage/.kodi/userdata/keymaps folder and edit line 201 to <subtitle>ShowSubtitles</subtitle>

    then reload keymaps with the kodi-send --action="reloadkeymaps" command.

    BTW. the positioning of subtitles (invoked by CTRL+t on keyboard ) does not work and AFAIK it never worked, also in manual mode the subtitle's positoning does not work.

    FYI after the upgrade from nightly-20241025-9f8eeb6 (RPi4.aarch64) to nightly-20241029-81a82b6 the PVR client (Tvheadend HTSP Client) couldn't run anymore. I suppose the plugins for RPi 4 are waiting for compilation. The revert to nightly-20241025-9f8eeb6 fixed the issue.

    Edit - the same issue even after the upgrade to LibreELEC-RPi4.aarch64-13.0-nightly-20241030-2f39556 which appeared in download section in the meantime.

    This can happen whenever I restart RPi via SSH?

    It shouldn't happen as the volumes should be unmounted properly during the restart AFAIK. The safer way is to unmount the problematic volume manually (see umount --help ).

    This can happen whenever RPi or HDD looses supply due to power interruption?

    Yes. You should avoid it, also disconnecting the USB/SATA adapter cable from RPi without unmounting, when the RPi is running, can lead to your issue.

    This was not happening on Odroid C2 because I was using older LE version with different kernel which was not doing that (flaging HDD as having errors and not mounting)?

    I suppose so.

    ...(RPi's never dies ;) ),...

    I understand your smiley face, so just FYI - unfortunately I had this bad experience with my RPi 4B/2G which died suddenly couple months ago, during the normal operation, without any obvious reason... Of course after the warranty period. It was properly cooled so never overheating.

    Just a black screen all of a sudden, did not boot anymore - most likely the Broadcom CPU itself died, pulling down the 3,3V to ~1,9V.

    Can someone please have a look at s.m.a.r.t. data and let me know if the HDD is dying?

    Looks like so far it's not so bad but you should always have your critical data backed up...

    See this link and the wikipedia link mentioned there for details:

    How Do I interpret HDD S.M.A.R.T Results?
    My laptop has recently started to become a bit unreliable, and for some reason I started to suspect that my HDD was starting to fail. After a bit of hunting on…
    askubuntu.com

    OK, so this is a "fix" for me. As I am using kodi-send with irexec, putting this block into /storage/.config/autostart.sh before irexec call fixes the issue.

    Code
    ### Temporary fix kodi-send bug
    cp /usr/bin/kodi-send /tmp/.
    cp /build/build.LibreELEC-RPi4.aarch64-13.0-devel/toolchain/aarch64-libreelec-linux-gnu/sysroot/usr/lib/python3.11/site-packages/kodi/xbmcclient.py /tmp/.
    export PATH=/tmp/:$PATH
    ### Temporary fix kodi-send bug

    It looks something has changed in some of recent updates (currently running 13.0-nightly-20240725-2cd39ba (RPi4.aarch64), issue observed on 13.0-nightly-20240720-ab27426 ) that broke kodi-send:

    # kodi-send
    Traceback (most recent call last):
    File "/usr/bin/kodi-send", line 27, in <module>
    from kodi.xbmcclient import *
    ModuleNotFoundError: No module named 'kodi'

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
    File "/usr/bin/kodi-send", line 30, in <module>
    from xbmcclient import *
    ModuleNotFoundError: No module named 'xbmcclient'

    Perhaps some paths needs to be updated?

    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...

    Reenabled the Weather add-on to confirm the issue reason but the Kodi crash did not happen anymore (on the same LE Nightly version as recorded in the latest log above... :)

    Now I plan to upgrade to LibreELEC-RPi4.aarch64-13.0-nightly-20240517-8f6f9a1 with the Weather add-on enabled and I'll see...

    Edit - after upgrade the issue reappeared... :) So I am disabling the Weather add-on (Gismeteo vl.maksime - 0.6.4+matrix.1) again...