cups.socket and cups.path are the old names (used before the upgrade).
Right. Removed already. Thanks.
Disable everything cups related by removing the symlinks. A find command should help you weed out stuff from before the upgrade:
find /etc/systemd/system/ -iname "*cups*"
Then, try reenabling and starting cups again. (Three symlinks should be created.)
systemctl enable org.cups.cupsd.service systemctl start org.cups.cupsd.service
Here is my current (working) configuration:
$ find /etc/systemd/system/ -iname "*cups*" /etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket /etc/systemd/system/printer.target.wants/org.cups.cupsd.service /etc/systemd/system/multi-user.target.wants/org.cups.cupsd.path
The note about the renamed service files is on the wiki [1].
Yes, thanks, I just didn't pay attention to the socket and path old units. Just the cups.service.
--Kyle Terrien
After disabling the remaining cups.socket and cups.path, rebooting, stopping and disabling org.cups.cupsd.service, and starting and enabling it again, I now don't see the dmesg cups stuff, thanks: % dmesg | 'grep' cups % However I still don't get cups working (not on the web interface, neither lpinfo): % sudo find /etc/systemd/ -name '*cups*' /etc/systemd/system/multi-user.target.wants/org.cups.cupsd.path /etc/systemd/system/printer.target.wants/org.cups.cupsd.service /etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket % lpinfo -v lpinfo: Bad file descriptor I noticed org.cups.cupsd.service just fails: % systemctl status org.cups.cupsd.service ● org.cups.cupsd.service - CUPS Scheduler Loaded: loaded (/usr/lib/systemd/system/org.cups.cupsd.service; enabled) Active: failed (Result: exit-code) since Tue 2014-11-04 21:24:58 CST; 8min ago Main PID: 7988 (code=exited, status=1/FAILURE) Nov 04 21:24:58 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:24:58 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:24:58 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. % journalctl -u org.cups.cupsd.service ... -- Reboot -- Nov 04 21:06:59 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:06:59 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:07:05 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:07:05 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Nov 04 21:12:41 m1 systemd[1]: Stopped CUPS Scheduler. Nov 04 21:16:12 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:16:12 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:16:12 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:16:12 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Nov 04 21:16:42 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:16:42 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:16:42 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:16:42 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Nov 04 21:24:58 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:24:58 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:24:58 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:24:58 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Notice I restarted it several times after some intermediate trials... if I run cupsd directly: % sudo cupsd cupsd: Child exited with status 1 Which is even more weird to me. cups named packages installed: % pacman -Qs cups local/cups 2.0.0-2 The CUPS Printing System - daemon package local/cups-filters 1.0.61-2 OpenPrinting CUPS Filters local/cups-pdf 2.6.1-2 PDF printer for cups local/lib32-libcups 1.7.5-1 The CUPS Printing System - client libraries (32-bit) local/libcups 2.0.0-2 The CUPS Printing System - client libraries and headers I tried re-installing cups and libcups with no sucees (just in case)... I'm still in the dark, sorry, :-( Thanks, -- Javier.