Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42824 - [cups] something is still depending upon the old "cups.service" unit file name.
Attached to Project:
Arch Linux
Opened by James (thx1138) - Monday, 17 November 2014, 22:49 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 18 November 2014, 03:56 GMT
Opened by James (thx1138) - Monday, 17 November 2014, 22:49 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 18 November 2014, 03:56 GMT
|
Detailscups 2.0.1-1
systemd 217-6 Reviewing the log file with "journalctl -b", kernel at loglevel=6, when cupsd is started, and after also, there are still systemd warnings in the log, such as: systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. systemd[1]: Cannot add dependency job for unit cups.path, ignoring: Unit cups.path failed to load: No such file or directory. systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Invalid argument systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Invalid argument systemd[1]: Cannot add dependency job for unit cups.service, ignoring: Invalid argument systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. "Something" is still looking for the old cups unit file names, particularly "cups.socket" and "cups.path", but I have not been able to find what. Some places I've tried grepping for "cups.socket": /usr/share/system-config-printer/ /usr/share/polkit-1/ /usr/share/foomatic/ /usr/share/cups/ /usr/share/hplip/ /usr/share/dbus-1/ /usr/bin/ /usr/lib/ No joy. Does anyone have suggestions about tracking these references to "cups.socket" and friends? I've filed a bug with systemd, for these "mystery" warnings, which fail to disclose the source of or trigger for the warning. But still, there should be some way to track these back to the cause. James |
This task depends upon
...
/etc/systemd/system/multi-user.target.wants:
total 8
drwxr-xr-x 2 root root 4096 Nov 16 15:51 .
drwxr-xr-x 7 root root 4096 Nov 14 23:05 ..
...
lrwxrwxrwx 1 root root 33 Apr 7 2014 cups.path -> /usr/lib/systemd/system/cups.path
...
/etc/systemd/system/printer.target.wants:
total 8
drwxr-xr-x 2 root root 4096 Oct 3 10:17 .
drwxr-xr-x 7 root root 4096 Nov 14 23:05 ..
lrwxrwxrwx 1 root root 36 Apr 7 2014 cups.service -> /usr/lib/systemd/system/cups.service
lrwxrwxrwx 1 root root 46 Oct 3 10:17 org.cups.cupsd.service -> /usr/lib/systemd/system/org.cups.cupsd.service
/etc/systemd/system/sockets.target.wants:
total 8
drwxr-xr-x 2 root root 4096 Oct 3 10:17 .
drwxr-xr-x 7 root root 4096 Nov 14 23:05 ..
lrwxrwxrwx 1 root root 43 Apr 7 2014 avahi-daemon.socket -> /usr/lib/systemd/system/avahi-daemon.socket
lrwxrwxrwx 1 root root 35 Apr 7 2014 cups.socket -> /usr/lib/systemd/system/cups.socket
lrwxrwxrwx 1 root root 45 Oct 3 10:17 org.cups.cupsd.socket -> /usr/lib/systemd/system/org.cups.cupsd.socket
/etc/systemd/system/sysinit.target.wants:
total 8
drwxr-xr-x 2 root root 4096 Aug 20 11:39 .
drwxr-xr-x 7 root root 4096 Nov 14 23:05 ..
So, maybe a note somewhere? Or, I missed a step on installing version 2.0.0 cups?
Should I add a note to the cups wiki? Are other people going to see these left-over links also?
So it's really already covered. You just forgot to disable the old services. You can add a note to the wiki if you want.