Hello again, The issue at hand does not occur on hosts where 'cups-browsed' is also installed (I guess the cups.service somehow gets "pulled in" by /etc/systemd/system/multi-user.target.wants/cups-browsed.service; I don't understand, however, how /etc/systemd/system/paths.target.wants/cups.path comes into play and prevent CUPS to start when 'cups-browsed' is missing, but not if it is installed).
I've been witnessing it, so far, on all three CUPS servers I have at hand, where 'cups-browsed' is not installed. 'hope this can help, Best, Cédric
