HP & Ghostscript - possible problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Greetings,

Until recently, printing with our HP 3015 was a cinch: all jobs were accepted.

Then in the last week (I think?) certain jobs (images in particular) have been rejected or failed.

Using the command:
su -c 'journalctl -u cups.service'  > troubleshoot-logs.txt

And then reading through the output, the consistent message that comes up is: Sep 14 10:55:44 pegasus cupsd[9287]: cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files" Sep 14 10:55:44 pegasus cupsd[9287]: [Job 1260] ./base/gsicc_manage.c:1244: gsicc_open_search(): Could not find default_rgb.icc Sep 14 10:55:44 pegasus cupsd[9287]: [Job 1260] | ./base/gsicc_manage.c:2025: gsicc_set_device_profile(): cannot find device profile Sep 14 10:55:44 pegasus cupsd[9287]: [Job 1260] GPL Ghostscript 9.24: Unrecoverable error, exit code 1 Sep 14 10:55:44 pegasus cupsd[9287]: [Job 1260] Page = 612x792; 12,12 to 600,780 Sep 14 10:55:44 pegasus cupsd[9287]: [Job 1260] slow_collate=0, slow_duplex=0, slow_order=0 Sep 14 10:55:44 pegasus cupsd[9287]: [Job 1260] This document does not conform to the Adobe Document Structuring Conventions and may not print correctly. Sep 14 10:55:44 pegasus cupsd[9287]: [Job 1260] ./base/gsicc_manage.c:1244: gsicc_open_search(): Could not find default_gray.icc Sep 14 10:55:44 pegasus cupsd[9287]: [Job 1260] | ./base/gsicc_manage.c:2025: gsicc_set_device_profile(): cannot find device profile Sep 14 10:55:45 pegasus cupsd[9287]: [Job 1260] PID 9941 (gs) stopped with status 1!
Sep 14 10:55:45 pegasus cupsd[9287]: Expiring subscriptions...
Sep 14 10:55:45 pegasus cupsd[9287]: [Job 1260] PID 9942 (pstops) exited with no errors. Sep 14 10:55:45 pegasus cupsd[9287]: [Job 1260] PID 9937 (/usr/lib/cups/filter/pdftops) stopped with status 1.
Sep 14 10:55:45 pegasus cupsd[9287]: [Job 1260] HP PS filter ENDS


"Unrecoverable error, exit code 1" seems to be key.

I noticed that the ghostscript rpm was updated on 9/5/2018; could this be the source of this problem, and has anyone else encountered something similar?

Much thanks,

Max Pyziur
pyz@xxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux