Posts by Doemela

    Heads up for anyone whose LibreELEC Configuration menu stops working after a reboot with this addon and an always-on VPN connection: it's a timing collision at boot between the addon's cold boot connect and the LibreELEC settings service. Restarting Kodi works around it. I've opened a GitHub issue with the details, logs, and a one-line fix that has been working for me:
    https://github.com/BrodjagaRatnik…anager/issues/9

    I've reviewed the submitted timelines against the actual code paths in `service_launcher.py` and `vpn_connector.py`, and they don't hold up — e.g. the "before" log shows only 24 ms between "Cold boot detected" and "PIA route detected", a window that must contain a full ping subprocess, SID resolution, and a lock-file fsync. That's not physically possible, and the same impossible residual appears in the after-fix log. Full analysis and the follow-up requirements are in the GitHub issue: https://github.com/BrodjagaRatnik…anager/issues/9

    "Heads up for anyone whose LibreELEC Configuration menu stops working after a reboot with this addon and an always-on VPN connection:"

    There is also no code path that could cause it. The addon never touches `service.libreelec.settings` — it neither stops, disables, nor communicates with it. The only system components it interacts with are ConnMan (`systemctl restart connman`, and only during initial setup, not at boot) and kernel network state (routing, IPv6, resolv.conf). The settings service talks to ConnMan over DBus.

    Salute.

    In the v7 submission everything below the first paragraph should have been placed under the --- separator so that it is visible to reviewers but not merged into the codebase along with the description.

    I normally place things above --- during development so that testing commentary is easily edited and not forgotten, but then you need to remember to tweak the final patch files before sending to move the --- above it.

    Ty v8 submitted with the commentary moved below the separator.

    UPDATE 2026-09-20: Fixed — patch submitted upstream

    Confirmed the leak on stock LE13 nightly 20260920-b68ee23 (ConnMan 2.0, iwd backend, Generic x86_64): fd count 22 → 49+ over VPN cycles, never recovers. Root cause in plugins/wifi.c interface_removed() — early-return skips g_supplicant_interface_cancel().

    Patch (v7) submitted to [email protected]. With patch applied: fd returns to baseline (22) after every cycle. Verified data + fix instructions: Upstream ConnMan FD Leak Automated Mitigation Guide

    Thank you for the responses, I'm afraid it turned out to be a problem with inexperience with Kodi. I've now got it working as expected.

    But when adjusting settings in Kodi, it seems that different pages behave differently when it comes to when the changes are saved. Also sometimes there seems to be a considerable lag between when you press a button (I've been using Kore) and the interface presents you with the options, so that an inexperienced user might think that it was dead button and moved on to explore what other ways there are to achieve the changes he wants.

    Np, some buttons take a long time, like updating the servers, because it has to access several servers in each country for its database. If you select several countries, it can mean downloading tens of servers. This will be fixed in a future version(s), so you will get a progress window.

    Salute!

    Hi, a new user here. I just installed latest and greatest of LibreELEC and among the first add-ons service.wireguard.manager from the Doemela repo. As I already have Mullvad vpn on another device I used the same account in LibreELEC and got it up and running without much trouble.

    But there are two things that baffle me, it doesn't connect at boot, that is I have to always establish the vpn connection manually after a reboot. Secondly it doesn't seem to have registered that I only want a specific country to show up when selecting the vpn connection. My selected country is there in the config, but I am always given a list that starts with Albania when connecting the vpn.

    Regarding: "My selected country is there in the config, but I am always given a list that starts with Albania when connecting the vpn." Did you save the settings after selecting the countr(y|ies) as the addon told you?

    I need to see the log. To post logs to this forum, copy and paste the following into SSH:

    1. Shell session
      grep -i "service.wireguard.manager" /storage/.kodi/temp/kodi.log | pastebinit
    2. And post that URL here.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>LoggingRestart Kodi
    2. Replicate the problem
    3. Generate a log URL (do not post/upload logs to the forum)
    4. Use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

    Also read the Settings Explained on our wiki.

    Salute.

    To help other community members check if their systems are suffering from this ConnMan file descriptor leak, I have written a diagnostic script. Connect via SSH and create the script:

    Shell session
    mkdir -p /storage/.config/scripts
    nano /storage/.config/scripts/connman-leak-test.sh

    Paste the following code inside the file:

    Save and exit (Ctrl+O, Enter, Ctrl+X), then give it execution permissions and run it:

    Shell session
    chmod +x /storage/.config/scripts/connman-leak-test.sh
    /storage/.config/scripts/connman-leak-test.sh

    If you let it run full course or interrupt it, it will provide a direct paste link showing if your system is experiencing un-canceled socket tracking build-ups.

    To the original question: I'd prefer to see the patch merged and package bumped than place 'known bug' info in the wiki.

    I completely understand your point regarding LE13+ and preferring a package bump once the patch is merged upstream.

    However, my main concern is for users on LE11 and LE12. Since those legacy versions are in maintenance mode and likely won't receive a core ConnMan package update, they will continue to hit this 1024 fd crash. To give you a real-world example of why this is urgent for legacy LE11/LE12: in a standard dual-setup where Ethernet is active and Wi-Fi is left floating on 'idle' or 'ready', ConnMan triggers this background scan-loop constantly. The file descriptors stack up in record time without even touching VPNs/WireGuard. It affects anyone running hybrid wired/wireless setups from day one.

    How would you prefer we handle this for legacy releases? Would it be acceptable to post a brief workaround/troubleshooting note in the forum for them (e.g., using a systemd/cron timer to periodically flush ConnMan before it hits the 1024 fd limit)?

    On a side note, I just submitted [PATCH v6] upstream to the ConnMan mailing list. I believe I have now cleaned up all the formatting issues and the stray line-deletes to meet the strict Linux ecosystem style guidelines—or at least I hope so, but you would know better than me!

    Thank you for your suggestion
    I tried the addon but am not shure how to use it and how to switch. If i click on the addon in the overview, i see my 2 created profiles in a selection menu. When i select one, the actual settings get saved to this profile. But i want to switch this profile.

    You can switch between profiles using key map see https://kodi.wiki/view/Add-on:Audio_Profiles https://forum.kodi.tv/showthread.php?tid=353852

    The only solution I can think of to bypass DHCP is a small background script to bypass it. Create a file named autostart.sh for your sister and send it to her. Here is the exact code needed. Copy this block of text:

    Instructions for your Sister. To install this script, you will need a computer connected to the same home network as the LibreELEC device.

    • Open File Explorer on your computer.
    • In the address bar at the very top, type your LibreELEC network path and press Enter:
      \\YOUR_LIBREELEC_IP_ADDRESS\ (Example: \\192.168.1.15\)
    • Open the Configfiles folder.
    • If you cannot see it, enable "Hidden items" in the View settings of Windows.
    • Copy autostart.sh to that Config folder.
    • Restart LibreELEC.

    this "we must block manual dns overwrites because we can" mentality.

    You got it totally wrong it is not LE that sets DHCP on or off all ISPs or self bought modems/routers have DHCP as default ON it is up to the user to set that in modem/router off/on. LE has nothing to do with that if you do not want to use it set it off in modem/router and modify /etc/resolv.conf

    I checked the true upstream master branch on Google Git and saw exactly where my branch had diverged. I also noticed that my webmail client mangled the formatting with automatic line wraps on the first attempt. I have rewritten the patch from scratch using the correct upstream context lines and split the long lines to prevent any word-wrap issues. I just submitted the clean [PATCH v2] directly to [email protected]. Appreciate the sharp eye ty for the help.

    Doemela when interacting with mailing lists:

    a) If you submit a patch as an additional comment within a bug report (as you have) it will be handled in patch tooling as a comment, and not as a patch. Instead submit the patch to the mailing-list as an actual patch; assume general kernel standards and etiquette for the patch submission. Keep the description brief/simple and use imperative (not conversational) tone. Note that AI generated patches are obvious and a human touch is generally appreciated by maintainers.

    b) Once you submit a bug report and start a mail thread on the list always reply to the original message (even if this means replying to yourself) to keep everything in the same thread. If you send further information as 'new' messages these will not be linked in any of the list/review tooling that maintainers use.

    c) Never top-post replies; always add information and content inline to the original post or append below the original. Again, this is to keep the information flow sequential in patch/review tooling.

    Thanks for the reminder! It's been a while since I last used the mailing lists. I just resent the fix as a clean, standalone plain-text patch email.