Created attachment 831332 [details] output from printer troubleshoot Description of problem: system-printer-config reports "filter failed" for any print job. Troubleshoot reads "sorry, no obvious solution" Version-Release number of selected component (if applicable): 3.11.9-200.fc19.x86_64 #1 Printer Canon-BJC-4200 How reproducible: Steps to Reproduce: 1. Start a print job (or $lp...) 2. job sent to the printer 3. a message appears "filter failed" Actual results: No printing Expected results: Printer working Additional info: Printer was working before the update. Troubleshoot output attached
I think that's a kernel version number. Did you print a file at the point the troubleshoot process asked you to? It doesn't record any file being printed. It would be really useful to see that debugging output from printing a file. If you aren't able to do that using the troubleshooter, just use "cupsctl --debug-logging", then print a file, then attach /var/log/cups/error_log. You can turn off debugging afterwards with "cupsctl --no-debug-logging".
Created attachment 833114 [details] error log
D [01/Dec/2013:20:34:55 -0300] [Job 112] Starting renderer with command: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=bjc600 -dPrintColors=15 -dProcessColorModel=/DeviceCMYK -dBitsPerPixel=24 -sPrintQuality=Normal -dMediaWeight=80 -sMediaType=PlainPaper -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 -r360x360 -sOutputFile=- /var/spool/cups/tmp/foomatic-JJnW1t D [01/Dec/2013:20:34:55 -0300] [Job 112] Starting process "kid3" (generation 1) D [01/Dec/2013:20:34:55 -0300] [Job 112] Starting process "kid4" (generation 2) D [01/Dec/2013:20:34:55 -0300] [Job 112] Starting process "renderer" (generation 2) D [01/Dec/2013:20:34:55 -0300] [Job 112] JCL: %-12345X@PJL D [01/Dec/2013:20:34:55 -0300] [Job 112] <job data> D [01/Dec/2013:20:34:55 -0300] [Job 112] renderer received signal 11 D [01/Dec/2013:20:34:55 -0300] [Job 112] Kid3 exit status: 1 D [01/Dec/2013:20:34:55 -0300] [Job 112] Sent 0 bytes... D [01/Dec/2013:20:34:55 -0300] [Job 112] PID 20113 (/usr/lib/cups/filter/foomatic-rip) stopped with status 9. I think that's saying ghostscript crashed. In fact, just running that command line does indeed crash: $ gdb --args gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dT -dNOPAUSE -dNOINTERPOLATE -sDEVICE=bjc600 -dPrintColors=15 -dProcessColorModel=/DeviceCMYK -dBitsPerPixel=24 -sPrintQuality=Normal -dMediaWeight=80 -sMediaType=PlainPaper -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 -r360x360 -sOutputFile=/dev/null [...] (gdb) r Starting program: /usr/bin/gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=bjc600 -dPrintColors=15 -dProcessColorModel=/DeviceCMYK -dBitsPerPixel=24 -sPrintQuality=Normal -dMediaWeight=80 -sMediaType=PlainPaper -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 -r360x360 -sOutputFile=/dev/null [...] Program received signal SIGSEGV, Segmentation fault. gs_setoverprint (pgs=0x63be98, ovp=0) at base/gsstate.c:711 711 if (profile_struct->sim_overprint == false) return; [...] (gdb) bt #0 gs_setoverprint (pgs=0x63be98, ovp=0) at base/gsstate.c:711 #1 0x0000003432dd211c in zsetoverprint (i_ctx_p=0x657d10) at psi/zcssepr.c:71 #2 0x0000003432d80272 in interp (pi_ctx_p=pi_ctx_p@entry=0x6053e0, pref=<optimized out>, perror_object=perror_object@entry=0x7fffffffd2f0) at psi/interp.c:1561 #3 0x0000003432d80d19 in gs_call_interp (perror_object=0x7fffffffd2f0, pexit_code=0x7fffffffcc40, user_errors=<optimized out>, pref=0x7fffffffcca0, pi_ctx_p=0x605480) at psi/interp.c:510 #4 gs_interpret (pi_ctx_p=pi_ctx_p@entry=0x6053e0, pref=pref@entry=0x7fffffffcd20, user_errors=<optimized out>, pexit_code=pexit_code@entry=0x7fffffffd2ec, perror_object=perror_object@entry=0x7fffffffd2f0) at psi/interp.c:468 #5 0x0000003432d75192 in gs_main_interpret (perror_object=0x7fffffffd2f0, pexit_code=0x7fffffffd2ec, user_errors=<optimized out>, pref=0x7fffffffcd20, minst=0x605340) at psi/imain.c:241 #6 gs_run_init_file (minst=minst@entry=0x605340, pexit_code=pexit_code@entry=0x7fffffffd2ec, perror_object=perror_object@entry=0x7fffffffd2f0) at psi/imain.c:552 #7 0x0000003432d756a2 in gs_main_init2aux (minst=minst@entry=0x605340) at psi/imain.c:289 #8 0x0000003432d75c0a in gs_main_init2 (minst=minst@entry=0x605340) at psi/imain.c:322 #9 0x0000003432d78478 in gs_main_init_with_args (minst=0x605340, argc=19, argv=0x7fffffffdec8) at psi/imainarg.c:241 #10 0x0000000000400a8f in main (argc=19, argv=0x7fffffffdec8) at psi/dxmainc.c:86
Created attachment 834836 [details] gs-bisected.patch 'git bisect' shows this to be the fix.
ghostscript-9.10-5.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ghostscript-9.10-5.fc19
ghostscript-9.10-5.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/ghostscript-9.10-5.fc20
Package ghostscript-9.10-5.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ghostscript-9.10-5.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23146/ghostscript-9.10-5.fc19 then log in and leave karma (feedback).
*** Bug 1027425 has been marked as a duplicate of this bug. ***
ghostscript-9.10-5.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
ghostscript-9.10-5.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
Identified the patch in the upstream GIT of Ghostscript and it is the patch which fixes bugs.ghostscript.com/show_bug.cgi?id=694154 GIT commit ID is 142b12b.