Kodi Community Forum
v19 LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: v19 LibreELEC Testbuilds for x86_64 (Kodi 19.0) (/showthread.php?tid=343069)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - succo - 2019-11-03

mmmh... there must be something strange happening with these builds... after the 12/10 stop i tried to update 3 times my le machines (1 pc and 1rpi2) and both produce unix_err:'67' error : 'Software  caused connection abort'
i see smb1 is not supported anymore, so made sure my smb machine had min version 3, but nothing changes
btw, everything is fine on the other machine running kodi in my network, a jetson nano with kodi built from sources (no le build for now) with the same date as the le release
what's up?

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Milhouse - 2019-11-04

New LibreELEC.tv Matrix build #1103: Generic
(Supercedes previous build)

SHA256 Checksum: a80d06de92bef318194de4a811163bd4dcc4ee101a643be3ace1845c7a02223e (Generic)

text:
# uname -a

Linux NUC 5.3.8 #1 SMP Sun Nov 3 21:03:20 GMT 2019 x86_64 GNU/Linux



# lsb_release

LibreELEC (Milhouse): devel-20191103210239-#1103-gcfe1640 [Build #1103]



# Kodi version

Kodi (19.0-ALPHA1 Git:cce8119). Platform: Linux x86 64-bit

Based on tip of LibreELEC.tv master (cfe1640, changelog) and tip of XBMC master (cce8119, changelog) with the following modifications: Build Highlights:
  1. Minors
Build Details:
  1. pvr.waipu:
    • Matrix fix ubuntu/debian packaging (PR:40, 2 commits, 2 files changed)
    • Matrix fix ubuntu packaging (2) (PR:41, 2 commits, 2 files changed)
  2. Additional commits/pull requests/changes not yet merged upstream:
    • Updated: [env] PR:3957 (perma): buildsystem: optimize for size when building with debug


RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Milhouse - 2019-11-04

(2019-11-03, 20:43)succo Wrote: mmmh... there must be something strange happening with these builds... after the 12/10 stop i tried to update 3 times my le machines (1 pc and 1rpi2) and both produce unix_err:'67' error : 'Software  caused connection abort'
i see smb1 is not supported anymore, so made sure my smb machine had min version 3, but nothing changes
btw, everything is fine on the other machine running kodi in my network, a jetson nano with kodi built from sources (no le build for now) with the same date as the le release
what's up?

'Software caused connection abort' is a known Samba issue that can occur depending on chunk size. The current chunk size used by Kodi has been chosen to minimise this issue, but it may still happen depending on your setup and what content you are accessing. I'm not seeing it myself with the new 4.11.1 Samba release (accessing Windows 7, FreeNAS 8.3 [Samba 3.2.x] and LibreELEC [Samba 4.11.1] servers), perhaps you can describe your setup in a little more detail (the OS/version of your SMB server, what type of content you are accessing, is it with all content etc.). And provide a kodi debug log.

Note that SMB1 is still available, it's just that with 4.11.x it's no longer enabled by default by samba.org, so now it's "official" and aligns with LibreELEC policy as we haven't been enabling SMB1 by default since LibreELEC 8.2, so chances are this change shouldn't make much difference to you, but what is important about the announcement is that SMB1 support *might* be removed entirely by samba.org in the future - ie. it's just a "heads up", and for users to start considering the replacement of their SMB1-only servers.

You can still enable SMB1 in the Kodi GUI Settings (SMB Client), same as before, if you really need it. And, once the LE Settings add-on returns, it can be enabled as a Samba Server option (but it still isn't recommended that you do so).

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Milhouse - 2019-11-04

Weekly Linux 5.4-rc6 build #1103x: Generic

Packages disabled/not included:
text:


digital_devices

dvb-latest

crazycat
Known issues:
text:


xf86-video-nvidia is untested

xf86-video-nvidia-legacy is not working reliably


RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - succo - 2019-11-04

(2019-11-04, 02:26)Milhouse Wrote:
(2019-11-03, 20:43)succo Wrote: mmmh... there must be something strange happening with these builds... after the 12/10 stop i tried to update 3 times my le machines (1 pc and 1rpi2) and both produce unix_err:'67' error : 'Software  caused connection abort'
i see smb1 is not supported anymore, so made sure my smb machine had min version 3, but nothing changes
btw, everything is fine on the other machine running kodi in my network, a jetson nano with kodi built from sources (no le build for now) with the same date as the le release
what's up?

'Software caused connection abort' is a known Samba issue that can occur depending on chunk size. The current chunk size used by Kodi has been chosen to minimise this issue, but it may still happen depending on your setup and what content you are accessing. I'm not seeing it myself with the new 4.11.1 Samba release (accessing Windows 7, FreeNAS 8.3 [Samba 3.2.x] and LibreELEC [Samba 4.11.1] servers), perhaps you can describe your setup in a little more detail (the OS/version of your SMB server, what type of content you are accessing, is it with all content etc.). And provide a kodi debug log.

Note that SMB1 is still available, it's just that with 4.11.x it's no longer enabled by default by samba.org, so now it's "official" and aligns with LibreELEC policy as we haven't been enabling SMB1 by default since LibreELEC 8.2, so chances are this change shouldn't make much difference to you, but what is important about the announcement is that SMB1 support *might* be removed entirely by samba.org in the future - ie. it's just a "heads up", and for users to start considering the replacement of their SMB1-only servers.

You can still enable SMB1 in the Kodi GUI Settings (SMB Client), same as before, if you really need it. And, once the LE Settings add-on returns, it can be enabled as a Samba Server option (but it still isn't recommended that you do so). 

ok, here we go... the smb share is on a dlink 340-l running Fonz Fun_Plug and the smbd --version response is Version 3.6.12
note that the same smb share is accessible from the kodi client running within ubuntu 18.04 (arm64) on the jetson but not from the libreelec clients (the 3 machines have the same sources/mediasources/guisetting files). In the afternoon I'm going to try with some other share in the network and see if i can browse them (browsing within LE errors all the way), and get some debug log
Tnx

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Milhouse - 2019-11-04

I mis-remembered the Samba version in FreeNAS 8.3.x, it is also Samba 3.6.12.

This version of Samba server only supports SMB2_02 which is a very old sub-protocol of SMB2. It certainly does not support SMB3.

When you configure SMB2 as the "Minimum protocol version" in the Kodi GUI (Settings > Services > SMB Client), this is configuring Samba with an alias (SMB2), which in Samba 4.x (ie. the version of the client Samba libraries used by LibreELEC) is mapped to sub-protocol SMB2_10 (SMB 2.10, Windows 7 SMB2 version) SMB2_02.

There are many versions of SMB sub-protocol, and the interpretation of the SMB2 alias may differ depending on the version of Samba client/server being used - for example SMB2 on your 3.x server maps to what became known as SMB2_02 (sub-protocols don't actually exist in 3.6.x).

Potted Samba history:

Quote:Samba 3.5.0 is the first 3.x release with experimental SMB2 support (sub-protocols weren't a thing at this time). There is no SMB3 support in 3.x.
Samba 4.0.0 introduces SMB2_10 (alias SMB2), the concept of sub-protocols (ie. SMB2_02), and initial SMB3/SMB3_00 support.
Samba 4.3.0 introduces SMB3_11 (the current default for the SMB3 alias).

When configuring a Samba 4.x client and Samba 3.6.x server to both use client/server min protocol = SMB2, the client will not be able to connect to the server - by selecting SMB2 you're selecting a sub-protocol on the client (SMB2_10) that is not supported by the server. The same is also true with SMB3 when mixing Samba 4.3.0+ client with a 4.x server version prior to 4.3.0.

Fortunately, the solution is fairly simple. Configure the min/max protocol in Kodi as follows:

Image

This will default Samba to client min protocol = SMB2 and client max protocol = SMB3 (the default "most common"/"best" min/max supported by the underlying Samba 4.11.x libs in LibreELEC) without adding the options to /storage/.kodi/.smb/smb.conf (note that this step isn't essential, as the next step should override whatever minimum protocol is set, but makes life a bit easier).

Then create /storage/.kodi/.smb/user.conf with the following line:
text:


client min protocol = SMB2_02

which should allow a Kodi client to connect to a Samba 3.6.12 server using a minimum sub-protocol of SMB2_02.

Let me know if that helps...

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - succo - 2019-11-04

still no way, and the log isn't outputting anything useful.
what i notice is that it logs something like
Code:
2019-11-04 20:08:54.321 T:1044   DEBUG: CUtil::GetMatchingSource: no matching source found for [smb://LANASSA/roba/SerieTV/]
2019-11-04 20:08:54.510 T:1044   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://USERNAME:PASSWORD@LANASSA/roba/SerieTV'
                                            unix_err:'67' error : 'Software caused connection abort'
2019-11-04 20:08:54.510 T:1044   ERROR: GetDirectory - Error getting smb://LANASSA/roba/SerieTV/
btw, if i look at the smbd log i see the connection started and closed from the LE ip
Code:
[2019/11/04 20:00:10.611384,  0] smbd/service.c:1150(make_connection_snum)
  CIFS: [192.168.1.20] connected to [roba] as user [xxxxxxx].
[2019/11/04 20:06:24.840756,  0] smbd/service.c:1419(close_cnum)
  CIFS: [192.168.1.20] closed the connection to service [roba].


RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Milhouse - 2019-11-04

(2019-11-04, 21:18)succo Wrote: still no way, and the log isn't outputting anything useful.

Are you sure this issue started with #1028?

I've tested the latest build (#1103 at time of writing) against my FreeNAS 8.3.x/Samba 3.6.12 server, and I'm not seeing any issues (so long as Kodi is configured with client min protocol = SMB2_02 etc.)

(2019-11-04, 21:18)succo Wrote: btw, if i look at the smbd log i see the connection started and closed from the LE ip
Code:
[2019/11/04 20:00:10.611384,  0] smbd/service.c:1150(make_connection_snum)
  CIFS: [192.168.1.20] connected to [roba] as user [xxxxxxx].
[2019/11/04 20:06:24.840756,  0] smbd/service.c:1419(close_cnum)
  CIFS: [192.168.1.20] closed the connection to service [roba].

CIFS? Is that the hostname of your LibreELEC/Kodi client?

Can you also confirm once more that your Samba server version is actually 3.6.12, as those log messages don't match the Samba source code (if you hand-typed the log, it could be typos, I guess). Unfortunately as the server log messages do not relate to any available Samba source code I'm a little dubious about your server - you could try increasing the server logging level (log level = 10 in smb.conf) and upload the log to somewhere.

Other than that, I'm really not sure what else to suggest, as I know for sure that a Samba 3.6.12 server can work with a Samba 4.11.x client, when configured correctly.

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Milhouse - 2019-11-05

New LibreELEC.tv Matrix build #1104: Generic
(Supercedes previous build)

SHA256 Checksum: a4d6fdc21572f9d6c7a6f024ab330391d289db656793aef6cf6fd250c7cc2f32 (Generic)

text:
# uname -a

Linux NUC 5.3.8 #1 SMP Mon Nov 4 21:10:16 GMT 2019 x86_64 GNU/Linux



# lsb_release

LibreELEC (Milhouse): devel-20191104210935-#1104-gcfe1640 [Build #1104]



# Kodi version

Kodi (19.0-ALPHA1 Git:a4dfad6). Platform: Linux x86 64-bit

Based on tip of LibreELEC.tv master (cfe1640, changelog) and tip of XBMC master (a4dfad6, changelog) with the following modifications: Build Highlights:
  1. pvr.iptvsimple - switch from RapidXML to Pugixml
  2. LibreELEC-settings: updated for Python3 (many thanks @edit4ever!)
    Quote:Please report here any issues with the LibreELEC Settings addon.

    For Python3 problems with all other add-ons, please report the issues to the add-on maintainer(s).
Build Details:
  1. XBMC:
    • [Android] fetchDisplayMode only for SDK>=24 (PR:16862, 1 commit, 1 file changed)
    • Fix CGUIDialogPVRGuideInfo::GetCurrentListItem crash (PR:16866, 2 commits, 2 files changed)
  2. pvr.iptvsimple:
    • Move from RapidXML to Pugixml which supports c++11 features + tvg-id fixes (PR:297, 6 commits, 25 files changed)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Updated: [env] PR:3957 (perma): buildsystem: optimize for size when building with debug
    • Added: [env] compare (perma): kodi: next
    • Added: [env] PR:3959 (perma): LibreELEC-settings: re-enable bytecode compilation
    • Added: [pkg] PR:143 (perma): Py3 conversion (service.libreelec.settings)


RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - succo - 2019-11-05

(2019-11-04, 22:55)Milhouse Wrote: Are you sure this issue started with #1028?
well, i tried the latest version before the stop and it worked, and it didn't when i tried the version from 30-10
(2019-11-04, 22:55)Milhouse Wrote: CIFS? Is that the hostname of your LibreELEC/Kodi client?
no, that's the protocol used to connect
(2019-11-04, 22:55)Milhouse Wrote: Can you also confirm once more that your Samba server version is actually 3.6.12, as those log messages don't match the Samba source code (if you hand-typed the log, it could be typos, I guess). Unfortunately as the server log messages do not relate to any available Samba source code I'm a little dubious about your server - you could try increasing the server logging level (log level = 10 in smb.conf) and upload the log to somewhere.

Other than that, I'm really not sure what else to suggest, as I know for sure that a Samba 3.6.12 server can work with a Samba 4.11.x client, when configured correctly. 
well, i'm sure smbd outputs 3.6.12 when run with --version, and that's what is in the logs. Tomorrow will try with loglevel 10 and will let you know
btw, thanks for the help and troubleshooting Smile

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Milhouse - 2019-11-05

(2019-11-05, 01:49)succo Wrote: no, that's the protocol used to connect

Right, but CIFS isn't technically a Samba protocol (closest would be NT1 aka "SMB1" in Samba, which should now be disabled by default on your client and server for security reasons). You'd be using CIFS if you were using OS/kernel mounts. Or a Windows client that still has SMB1 enabled. But not LibreELEC with smb://, as that's not technically capable of making a "CIFS" connection.

(2019-11-05, 01:49)succo Wrote: well, i'm sure smbd outputs 3.6.12 when run with --version, and that's what is in the logs. Tomorrow will try with loglevel 10 and will let you know

The only reason I'm querying the version of your server is because the messages from your log don't exist in the Samba tree (I've checked every released version). It's possible your vendor has applied custom patches. Or you mistyped them if you aren't cutting & pasting. The possibility of vendor patches makes me wonder what else might have been changed. It might also be nothing. Who really knows, it's Samba... Sad

Anyway, assuming it is a genuine 3.6.12 Samba release, make sure your server has the following configured in its smb.conf:
text:


min protocol = SMB2

max protocol = SMB2

Note: with your vintage of server there's no server or client prefix for the above options. Also there's no point trying to enable support for SMB3 as this will fail (not yet invented).

Without the above options your server will only accept NT1 and lower connections (ie. CORE), and won't accept SMB2 connections. And yep, as if this couldn't be any more complicated, SMB1 isn't really a protocol in the wonderful world of Samba - it's known as NT1...

I now strongly suspect the lack of these server options is the reason for your "software connection abort" issue - it just so happens that previously you were somehow connecting from LibreELEC and Jetson Nano with NT1 (aka "SMB1"), not SMB2_02. With 4.11.x the default client min (sub-)protocol is now SMB2_02, and not CORE as it used to be prior to 4.11.0.

As mentioned previously, SMB2 on your 3.6.x server isn't an alias, but will correspond to the SMB2_02 sub-protocol on a Samba 4.x client.

You might also want to add:
text:


nt pipe support = no
to your 3.6.x server smb.conf to prevent a remote code execution security exploit.

A small correction to my earlier post: In Samba 4.11.0, the default client min protocol is now SMB2_02 (up from CORE), so in theory, with a Samba 4.11.x client, you should not need to configure any Kodi SMB Client settings (including user.conf) for Kodi to connect with your Samba 3.6.12 (or better) server (although you will need to enable min protocol = SMB2 on the server, as detailed above). The defaults should work fine, so long as your server is configured to accept SMB2 connections.

I don't know what version of Samba client library is on your Jetson Nano, but once you configure min protocol = SMB2 on your server you will more than likely discover that the Nano can no longer connect to the server unless you configure it in Kodi SMB Client as follows:

* Samba client library < 4.0.0: "Minimum protocol version" and "Maximum protocol version" both set to SMB2
* Samba client library >= 4.0.0 and < 4.11.0: "Minimum protocol version" and "Maximum protocol version" both set to None; add client min protocol = SMB2_02 to .kodi/.smb/user.conf
* Samba client library >= 4.11.0: "Minimum protocol version" and "Maximum protocol version" both set to None

You can run testparm -vs /storage/.kodi/.smb/smb.conf | grep protocol in LibreELEC to confirm your current client settings.

To view your LibreELEC Samba server (if enabled) and non-Kodi client settings, use testparm -vs /run/samba/smb.conf | grep protocol.

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Fourweddings - 2019-11-05

(2019-11-05, 00:09)Milhouse Wrote: New LibreELEC.tv Matrix build #1104: Generic(Supercedes previous build)
​​
Can confirm that #1104 is working with “LibreELEC-settings: updated for Python3 (many thanks @edit4ever!)” on Intel NUC. 
NUC6i5SYB, BIOS SYSKLi35.86A.0065.2018.0103.1000 01/03/2018.
LibreELEC settings seems to be working fine, as well as general Kodi.

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - SirMacke - 2019-11-05

Had to back down to #1007 (latest working, 1-3 higher might work, have not tested yet)
The later ones gives 10+ error when Kodi has started. Netflix error, log error, this and that app error.
Most apps won't start. Not even the Log viewer lol.
No log at the moment, will try to get one.

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - Milhouse - 2019-11-05

(2019-11-05, 10:29)SirMacke Wrote: Had to back down to #1007 (latest working, 1-3 higher might work, have not tested yet)
The later ones gives 10+ error when Kodi has started. Netflix error, log error, this and that app error.
Most apps won't start. Not even the Log viewer lol.
No log at the moment, will try to get one.
Python 3 problems are to be expected, contact the add-on maintainers for an update.

RE: LibreELEC Testbuilds for x86_64 (Kodi 19.0) - succo - 2019-11-05

ok, i simply updated samba to 3.6.25 on the nas and now everything has come back to normal

thanks @Milhouse for the help