Suddenly my Samsung printer fails to print with the following error in the CUPS log…
W [18/Aug/2023:15:34:40 +0200] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [18/Aug/2023:15:34:41 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [18/Aug/2023:15:34:41 +0200] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [18/Aug/2023:15:35:21 +0200] [Job 10] Grayscale/monochrome printing requested for this job but Poppler is not able to convert to grayscale/monochrome PostScript.
W [18/Aug/2023:15:35:21 +0200] [Job 10] Use "pdftops-renderer" option (see cups-filters README file) to use Ghostscript or MuPDF for the PDF → PostScript conversion.
It was working fine before my last “dup”. I don’t understand how I can “Use "pdftops-renderer" option” and can’t locate the cups-filters README file. The printer was setup with YaST and I have tried both drivers offered to print a test page. It’s a great printer and I am not about to change it.
I was wrong about it being a hardware problem as it works under Windows 10. I tried one more time after I had deleted the printer and was trying to re-configure using YaST. It now reports “Cannot access cupsd on ‘localhost’” and can’t start the CUPS daemon.
Box2:/home/ion # lpstat -h localhost -r
scheduler is not running
Box2:/home/ion #
Unable to connect
Firefox can’t establish a connection to the server at 127.0.0.1:631.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.
I assume you must try to concentrate on this “suddenly”. It may appear to you as “suddenly”, but most of the cases something was done, like update. change hardware, whatever.
But the same logic applies. What changed between the last time “it worked” and the first time it didn’t. I know that is not always obvious, but nevertheless it could be important.
Earlier in the thread you reported cupsd was active when you ran sudo systemctl status cups. The service uses socket and path based activation, so may only be active when triggered first.
Box2:/home/ion # sudo systemctl status cups.{service,socket,path}
● cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; preset: enabled)
Active: active (running) since Fri 2023-08-18 22:04:50 CEST; 12min ago
TriggeredBy: ○ cups.path
● cups.socket
Docs: man:cupsd(8)
Main PID: 15905 (cupsd)
Status: “Scheduler is running…”
Tasks: 1
CPU: 1.115s
CGroup: /system.slice/cups.service
└─15905 /usr/sbin/cupsd -l
Aug 18 22:04:50 Box2 systemd[1]: Starting CUPS Scheduler…
Aug 18 22:04:50 Box2 systemd[1]: Started CUPS Scheduler.
Aug 18 22:12:20 Box2 cupsd[15905]: gkr-pam: unable to locate daemon control file
Aug 18 22:12:20 Box2 cupsd[15905]: gkr-pam: stashed password to try later in open session
● cups.socket - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.socket; enabled; preset: enabled)
Active: active (running) since Fri 2023-08-18 22:04:50 CEST; 12min ago
Triggers: ● cups.service
Listen: /run/cups/cups.sock (Stream)
CGroup: /system.slice/cups.socket
Aug 18 22:04:50 Box2 systemd[1]: Listening on CUPS Scheduler.