From: ldo@nz.invalid   
      
   On Sun, 28 Dec 2025 22:17:27 +0100, Carlos E.R. wrote:   
      
   > This happened to me recently:   
   >   
   > Telcontar:~ # systemctl status smb   
   > × smb.service - Samba SMB Daemon   
   >       Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; preset:   
   disabled)   
   >       Active: failed (Result: exit-code) since Wed 2025-12-17 23:09:54 CET;   
   19h ago   
   >         Docs: man:smbd(8)   
   >               man:samba(7)   
   >               man:smb.conf(5)   
   >      Process: 2479 ExecStartPre=/usr/share/samba/update-apparm   
   r-samba-profile (code=exited, status=1/FAILURE)   
   >          CPU: 77ms   
   >   
   > Dec 17 23:09:54 Telcontar systemd[1]: Starting Samba SMB Daemon...   
   > Dec 17 23:09:54 Telcontar update-apparmor-samba-profile[2479]: generating   
   profile sniplet failed   
   > Dec 17 23:09:54 Telcontar systemd[1]: smb.service: Control process exited,   
   code=exited, status=1/FAILURE   
   > Dec 17 23:09:54 Telcontar systemd[1]: smb.service: Failed with result   
   'exit-code'.   
   > Dec 17 23:09:54 Telcontar systemd[1]: Failed to start Samba SMB Daemon.   
   > Telcontar:~ #   
   >   
   > I was baffled. I asked ChatGPT:   
      
   Or you could have looked further into the log with journalctl, and   
   seen the appropriate message there.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)