![](https://seccdn.libravatar.org/avatar/0f88cf8bb979996f217ccb046ece82ea.jpg?s=120&d=mm&r=g)
Thanks!
The 'disable spoolss = yes' did the trick for me. I already had
everything else related to printing disabled, but smb still wouldn't
start.
It might be related to the apparmor profile for samba, because I got a
'permission denied' error in my 'systemctl status smb' output...
On Wed, Feb 2, 2022 at 11:04 AM cagsm
On Wed, Feb 2, 2022 at 9:28 AM Carlos E. R.
wrote: On 2022-02-02 04:45, Larry Len Rainey wrote:
Samba broke in todays 15.3 update - is it apparmor or bug? Status: "daemon failed to start: Samba failed to init printing subsystem"
same here with the smb.service giving this error after the latest samba patches from some hours ago. as I have not changed anything on the machine and suddenly samba dieing it took me while to figure out a work around. some several years old hits on the interwebs search wrote about simply disabling printing stuff in smb.conf
they advised about adding the line in the global section:
disable spoolss = yes
to smb.conf. and i also disabled some other print stuff such as
# printing = cups # printcap name = cups # printcap cache time = 750 # cups options = raw
i dont use any kind of printer on or with the machine.
these settings helped so far. dunno why samba patches need to bring down the whole samba :( ty.
-- Met vriendelijke groet / Best regards, Wilfred van Velzen