LE 11 nightly - Samba not showing share list

Known issue - https://github.com/LibreELEC/Libr…ment-1079720666

issue raised on samba email list -

• https://lists.samba.org/archive/samba/2022-March/240221.html

heitbaum do you think that enabling "DEBUG=samba" will help getting more helpful logs?

I worked on a samba patch last night. https://github.com/heitbaum/Libre…21b70f0f1c06fa1

If you are going to debug/test samba. You will need this proposed upstream patch.

I was going to try and find some time to investigate when it was introduced before going down the route debug. We know it happened between 4.15 and 4.16 (with 4.15.6 working fine - so not a recent / backported patch.)

I think this regression is in the cleanup around this commit - smbd: Remove unused "struct connections_key" - https://http://bugzilla.samba.org/show_bug.cgi?id=14999

Just tested with your upstream patch ,still not working.Here's the log .

The build was compiled with DEBUG=samba ,so let me know if there's a better way to gather some useful logs from this build.

I believe the issue is in smbd. So something like

systemctl stop samba

smbd -i -d xx

Test via smbclient -L

Quote from heitbaum

I believe the issue is in smbd. So something like

systemctl stop samba

smbd -i -d xx

Test via smbclient -L

Here you go --> smbd log

Nightlies are experimental development images so users should expect bugs and delays in fixing things. Our normal preference is to report the fix and then bump to include the resolution patch or another bump rather than revert back. If it becomes clear the issue won't be resolved quickly, then we'll revert the version.

Quote from nvdias

What is the best apoach to compile the current nightly but ignoring the last samba update ?

Will patching packages/network/samba/package.mk (for the old 4.15.6 ) be enough ?

followed by:

PROJECT=RPi DEVICE=RPi4 ARCH=arm scripts/clean samba

PROJECT=RPi DEVICE=RPi4 ARCH=arm scripts/clean heimdal

PROJECT=RPi DEVICE=RPi4 ARCH=arm make image

?

thanks

Display More

You may try that approach, but last time i tried (right after the bug was discovered) that approach , it failed to build samba with both 4.15.6 and 4.16 RC1.

For me the best workaround until this is fixed, was to add the "storage" path to /storage/.config/samba.conf.

Then connect the samba clients with that path (e.g. //server_ip/storage).