core-agent-linux/vm-systemd/cups.service.d/30_qubes.conf

[Unit]
ConditionPathExists=/var/run/qubes-service/cups
After=qubes-sysinit.service

[Service]
ExecStartPost=/usr/lib/qubes/init/control-printer-icon.sh
systemd: while disabling service, disable also its activators This time it is for cups, which have socket-based and path-based activators. When activator tires to start the service which is disabled by condition file it enters infinite loop (as service wont start, but will not report an error). 2013-12-16 21:10:37 +01:00			`[Unit]`
			`ConditionPathExists=/var/run/qubes-service/cups`
systemd: order units checking for qubes-service after qubes-sysinit Files in /var/run/qubes-service are created by qubes-sysinit.service. So defer that condition check after that service start. Thanks @adrelanos for the report. Fixes QubesOS/qubes-issues#1985 2016-05-12 00:15:14 +02:00			`After=qubes-sysinit.service`
Clean up early initialization and setup of /rw 2016-10-22 17:43:16 +02:00
			`[Service]`
			`ExecStartPost=/usr/lib/qubes/init/control-printer-icon.sh`