Posts by heitbaum

    If in your LibreELEC.tv directory you do the following, that patches to fix the compile error will be added.


    Code
    wget https://github.com/LibreELEC/LibreELEC.tv/pull/9163.patch
    git am 9163.patch

    # or the following if you are not using a git clone

    Code
    patch -p1 < 9163.patch

    I have done a test using noble (with host gcc 14) and needed the 3 patches in my gcc-14 branch (as I had expected) I needed to remove openjdk-21-jre-headless and use openjdk-17-jre-headless

    Commits · heitbaum/LibreELEC.tv
    Just enough OS for KODI. Contribute to heitbaum/LibreELEC.tv development by creating an account on GitHub.
    github.com

    Then did scripts/build kodi

    The build was successful

    Note: le11 11.0.6 was built with the jammy docker image in our GitHub Actions.

    duncang92 we are trying to test this ssl issue, and can’t reproduce it yet.


    Can your please confirm the password to your mariadb matches between the advancedsettings.xml and the mariadb. The password won’t be “kodi”. Please don’t share your password here - but it should be the ddddd line.

    please also test the following line - it should let you in to the database.
    # mariadb -h 192.168.68.51 --skip-ssl-verify-server-cert -u kodi -p

    In LE we have fixed/worked around …. the connector change and the fact that 3.4 can only work with a verified ssl connection.

    The below patch to Kodi “should” fix Kodi to alway “not verify” ssl (thus allowing non sls too). I have not submitted it upstream as I have not “fully tested it”.

    Atm the latest Pi nightly is from 2024-06-23 with latest update from 2024-06-22 which means the latest 8 changes haven't triggered a new build, any problems?

    CI doesn’t really like [does not have capacity to] building both LE12 and LE13 on the same day. (And addons.)

    in addition the generic builds overrun their 6 hour allotment so these have been missing out a bit. The overrun when the new job cancels the old being the most distracting.


    I have cleared the backlog - so “all” 🤞LE13 nightlies are queued for build.

    Looks ok here

    Looks like this works:

    Thanks for testing vpeter - for the time being (as this needs a Kodi change) this will need to be the workaround.

    It looks like the client has changed the “failure logic”

    [MDEV-28634] Client's --ssl-* options (without --ssl-verify-server-cert) are silently ignored if TLS is not possible - Jira
    >> The client will only see an error if they also provide the --ssl-verify-server-cert option:<<

    I believe the correct fix would be to set sslMode=disabled in the connection from Kodi - as in https://mariadb.com/kb/en/using-tl…java-connector/ (will be the same with c connector I believe)
    By default when sslMode is set (not disabled), connector will use "serverSslCert" is set or the default truststore if not. Using default truststore can be disable setting option "fallbackToSystemTrustStore" to false.

    Can you confirm it forces ssl or forces ssl verification?

    these are the changes

    Comparing v3.3.10...v3.4.0 · mariadb-corporation/mariadb-connector-c
    MariaDB Connector/C is used to connect applications developed in C/C++ to MariaDB and MySQL databases.The client library is LGPL licensed. - Comparing…
    github.com

    and this one is the force ssl verification.

    Here are the ssl stuff from mariadb and there seems to be some require per user. Without seeing the logs I could not comment further. But is your connection running ssl (and just without the verify?) and it fails with the connector 3.4 (due to the verify) - the comments should be pretty useful in isolating this.

    Securing Connections for Client and Server
    Enabling TLS encryption in transit on both the client and server.
    mariadb.com

    I don’t understand the conversation around the shared library. There has never been a link to /usr/lib for the shared library in LE. The other binaries are correctly linked to the shared library as can be shown by using ldd. I have tried running boblightd via trace and can’t see the library being imported dynamically. Can you please share where you think the dynamic library is being used.

    I can see the process running as below (which wouldn’t run if a library is missing.) I can’t run it myself as I don’t have the serial interface that boblightd communicates too.


    nuc12:~ # systemctl status service.multimedia.boblightd | cat
    ● service.multimedia.boblightd.service - boblightd
    Loaded: loaded (/storage/.config/system.d/service.multimedia.boblightd.service; enabled; preset: disabled)
    Active: active (running) since Mon 2024-05-06 13:37:48 UTC; 22s ago
    Main PID: 1958390 (boblightd)
    Tasks: 2 (limit: 36590)
    Memory: 856.0K (peak: 1.5M)
    CPU: 32ms
    CGroup: /system.slice/service.multimedia.boblightd.service
    └─1958390 boblightd -c /storage/.kodi/userdata/addon_data/service.multimedia.boblightd/boblight.conf

    May 06 13:37:48 nuc12 systemd[1]: Started service.multimedia.boblightd.service.
    May 06 13:37:48 nuc12 sh[1958414]: cp: can't stat '/storage/.kodi/addons/service.multimedia.boblightd/config/*.sample': No such file or directory