Just competed an update to 6.7.0 on my Neon box and now Samba is failing to enable and just gives me an error of “Timed out waiting for smbd.service to start.”
Tried a clean install and same issue, loaded an older ISO of neon from 20260528 and works fine. I haven’t had a chance to dig into the issue but figured a heads up for other users may be of benefit.
have a look at the service status systemctl status smbd.service for a clue why it is failing. If there is not enough info then look in the journal journalctl -b 0 -u smbd.
I assume you will see an error reported. What do you see?
Edit: On my Fedora system the service is called smb.service not smbd.service`. Check for both service names.
Tried troubleshooting from the command line and smbd seem to be failing to start because of the comment on this line in neon-usershares-smb.conf
usershare allow guests = yes # optional line
so I removed the comment and was able to successfully start the smbd service. Unfortunately this was not the only issue.
neon-usershares-smb.conf points to the directory usershare path = /var/lib/samba/sambashares which didn’t exist but I did have an usershares directory. So I changed the path to
path = /var/lib/samba/usershares
Checked the sharing dialog and it was giving me an error that the sambashare group needed write access to usershares, so I gave the group write access and it now appears to work fine. I haven’t done any further tests.
I should note that I’m using the Dolphin filesharing plugin and this was on the neon-user-20260528 install that I updated to neon-user-20260616.
Traced it back to the following “setup support bits for samba usershares”
Apparently samba doesn’t like inline comments and the usershare path in is pointing to the incorrect path in neon-usershares-smb.conf, should be /var/lib/samba/usershares.
The user permissions may have to be changed to 1757 in the post install script. I’m not sure of the risk of this permission change so I could be very wrong.