I use Samba for one task only, to transfer files from my Manjaro laptop to an old Windows 7 machine in my workshop that drives the CNC machines.
My configuration is described in this topic, the last post: Trying to set up a shared public folder with Samba ("Windows cannot access //COMPUTERNAME")
Sometimes (rather unpredictably, at least to my pattern recognizing abilities), but often enough to be an inconvenience, this workshop machine fails to see my laptop listed in the workgroup, as if it was not powered on.
sudo systemctl enable --now smb nmb typically fixes the issue, so this is more of a minor inconvenience than a real problem.
However, last time this happened (20 minutes ago), instead of running the above command I tried
systemctl --failed just to see what's going on:
UNIT LOAD ACTIVE SUB DESCRIPTION ● nmb.service loaded failed failed Samba NMB Daemon LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed.
Of course, after running
sudo systemctl enable --now nmb the problem was fixed (at least temporarily) and
systemctl --failed returned the usual "0 loaded units listed".
Is there a more permanent fix for this? Like I said, it's not a major issue, but an inconvenience. I don't even know how to reproduce the problem, sometimes it works, sometimes it doesn't.