Launchpad has imported 12 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1036428.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-12-01T23:59:52+00:00 veidea wrote: Created attachment 831332 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/0 ------------------------------------------------------------------------ On 2013-12-02T11:15:26+00:00 Tim wrote: 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". Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/1 ------------------------------------------------------------------------ On 2013-12-05T12:13:27+00:00 veidea wrote: Created attachment 833114 error log Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/2 ------------------------------------------------------------------------ On 2013-12-05T13:20:45+00:00 Tim wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/3 ------------------------------------------------------------------------ On 2013-12-10T15:25:13+00:00 Tim wrote: Created attachment 834836 gs-bisected.patch 'git bisect' shows this to be the fix. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/4 ------------------------------------------------------------------------ On 2013-12-10T17:28:34+00:00 Fedora wrote: ghostscript-9.10-5.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ghostscript-9.10-5.fc19 Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/5 ------------------------------------------------------------------------ On 2013-12-10T18:27:38+00:00 Fedora wrote: ghostscript-9.10-5.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/ghostscript-9.10-5.fc20 Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/6 ------------------------------------------------------------------------ On 2013-12-11T02:02:43+00:00 Fedora wrote: 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). Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/7 ------------------------------------------------------------------------ On 2013-12-11T10:48:56+00:00 Tim wrote: *** Bug 1027425 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/8 ------------------------------------------------------------------------ On 2013-12-20T02:02:30+00:00 Fedora wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/9 ------------------------------------------------------------------------ On 2014-02-26T13:52:07+00:00 Fedora wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/10 ------------------------------------------------------------------------ On 2014-06-26T17:54:13+00:00 Till wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1334712/comments/13 ** Changed in: ghostscript (Fedora) Status: Unknown => Fix Released ** Changed in: ghostscript (Fedora) Importance: Unknown => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1334712 Title: gs segfault while printing Status in GS-GPL: Unknown Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: Fix Released Status in ghostscript package in Fedora: Fix Released Bug description: OS : Lubuntu 14.04 32 or 64 bit Printer : Canon BJC 4100 ghostscript 9.10~dfsg-0ubuntu10.1 Can't print, filter failed Seems to be the same as https://bugzilla.redhat.com/show_bug.cgi?id=1036428 [Impact] With certain drivers/printers it is impossible to print. [Test Case] Run the following command line (from the Red Hat bug report) in a terminal window: 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 Without the fix Ghostscript crashes with a segmentation fault, with the proposed package Ghostscript does not crash any more. [Regression Potential] Very low, the patch are trivial NULL checks. To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1334712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
