Posts by nars

    In the mean time I did also used pngcrush on mines to recompress and get rid of photoshop metadata and I did also reduced them significantly. Most are actually <10KB... total 2.5MB of 251 picons... anyway no change at all. Btw, these are my picons: Zippyshare.com - nos_cabo_220x132_nologo.rar

    Honestly I don't really think it is in any way related to file size... note that I said I get problem even with local kodi running on same RPi2 as tvheadend (as well as in a remote RPi connecting to that same tvheadend) BUT no problem at all with Kodi running on Windows PC and connecting to the same tvheadend on the RPi2...

    In the mean time I did also setup a RPi3 for a friend and again re-did some few tests with this with a completely clean Libreelec... and I did even test it with tvheadend42 also running on that new RPi3... same exact problem!

    One thing that I should say is that once picons are cached on kodi (after long time waiting to fetch them all) then they allways show ok, but if I clean icons cache on tvheadend (that causes icon number to change on the /imagecache/nnn urls) then kodi will also need to fetch them all again and same delays and timeouts appens again.

    I'm really surprised that no one else reports same problem... I'm having it since OE6 at least, did clean installs etc and can always reproduce it.

    Besuz: In your case are you running Libreleec (with tvheadend) on a RPi? (I ask it as I can't reproduce it on kodi running on Windows then it may be either RPi or Linux specific, not sure) and in your tvheadend in Configuration -> General -> picons path, you have it set as file:///storage/folder_with_your_picons... or and http url to a 3rd party http server with the picons?

    Thanks for your reply.

    If you see that line for 'nbtstat -a LibreELEC' then LibreELEC is acting as smb master browser on your LAN. I'm not sure what change of the ones I described you made:
    - if you enabled port 445 and 139 to allow it to work properly as master browser, then it's normal it sill shows like that...
    - if you disabled 'local master' to just prevent LibreELEC to become master browser then something is not OK for sure.
    In either case note that you must restart LibreELEC after changing samba config... and if you still have problems then yes you may try to restart other PC's, as I remember that on W7 (at least) sometimes after problems with weird configs then devices will not show anymore on the 'Network' folder until restart... thought they would show on 'net view' if I remember correctly.

    escalade: sorry if I didn't made myself clear, English is not my native language, I did tried to explain the issue in detail, but maybe it got too long and not fully clear I did just edit my 1st post to make it clear that I did test it.

    mikeboss: Yes, I can also confirm that OE 6 / LE 7 uses same exact samba config, I did compare it myself before. The random problems that you get may be related to the issue I report on the 1st post... it may work ok when LE device is not yet elected the master browser, but after you turn off other PC's, etc... (it all depends on the other smb devices on your LAN) then LE will eventually become master browser... then the problems will start. Anyway you may test to create /storage/.config/samba.conf (just copy the sample file there) and change (or comment with starting #) the 'smb ports' line.

    I have LibreELEC 7.02 with tvheadend 4.0.9 running on rpi2 for some time, all works fine I should say, however recently I added picons on tvheadend and I'm having an issue, local kodi running on the same rpi (as well as a remote kodi on other rpi) apparently haves some problem fetching picons from tvheadend, it takes very long time for them to show on the channels list and looking at kodi log apparently I could see that it tries to fetch a few ones simultaneously (pipelining) and there are some 10sec. timeouts that I guess explain the long delays to get picons...

    As I said above I have a 2nd rpi on the LAN that also connects to tvheadend on the 1st rpi and this 2nd rpi shows exactly same issue, Kodi very slow to fetch picons. However I have also Kodi on a Windows PC also connecting to tvheadend on the 1st rpi and on this one picons fetch instantaneously for all channels.

    I question to myself... is this a Kodi bug? but no problem at Kodi on the Windows PC... only at LibreELEC on my rpi's... some curl lib related problem with that pipelined access method?

    I'm attaching my kodi log. Note that I enabled debug (incl. curl debug) only at 04:27:08, then I did browse channels list on kodi and it started fetching picons... timeouts at 04:28:11...

    Any ideas please?


    You can put your own config file in /storage/.config/samba.conf to test your theory. It will override the default /etc/samba/smb.conf.

    Yes, I know that and I did surely test it before posting my fix suggestion With NetBIOS (139) port enabled it works perfect as master browser, all pc's are able to get Workgroup devices list with no problems at all.

    My suggestion is just for developers to fix it as default as I guess it causes trouble to a lot more users.

    For some time now I knew that there was something wrong with LibreELEC (and OpenELEC) samba, but only now I decided to look at it in detail and try to find the real reason...

    The issue is that if we just connect a LibreELEC device (with default config) on a LAN with Windows machines (in my case W7 and XP pc's) as soon as the LibreELEC device is elected the smb master browser (and this is easy after short time, with the current samba config on it...) then problems start, Windows machines can no longer browse Workgroup and properly see other smb devices/pc's on the LAN.

    (though note that some may be cached for some time on "Network" folder on W7 at least... and it may seem tricky... but 'net view' shows them with no cache apparently, then easy to test)

    Example, you can see LibreELEC is master browser and 'net view' can't show devices list:

    I used to just edit OE samba config and set 'local master = no' to prevent it becoming local master (and I could find a few other posts on OE forum about doing same), thus avoiding the problem, however now that I did a clean LibreELEC install I decided to do further research and some tests about this... and... I'm very confident that the reason for this is that stock LibreELEC samba config defines 'smb ports = 445' instead of the samba default 'smb ports = 445 139'... i.e. disabling port 139 means no NetBIOS is available (force using Direct-hosted smb only), however then it just doesn't work as NetBIOS browser service and thus it cannot be the master browser or it breaks browsing Workgroup devices on the whole LAN.

    My suggestion to fix the problem (and yes, I did fully test it before posting this) is either replace 'smb ports = 445' to 'smb ports = 445 139' (or just omit that 'smb ports' line completely, as this is the samba default anyway...) OR if you really want to keep NetBIOS disabled for some reason (I don't see what one honestly, as both are supposed to be always available and devices should auto-negociate and use Direct-hosted vs NetBIOS automatically) then just set 'local master = no' to prevent LibreELEC device to participate on elections for master browser.