Ubuntu
ghostscript package

gs segfault while printing

Bug #1334712 reported by zefox on 2014-06-26

This bug affects 1 person

	Status	Importance	Assigned to
GS-GPL	Unknown	Unknown	gs-afpl-bugzilla #694154
ghostscript (Fedora)	Fix Released	Critical	redhat-bugs #1036428
ghostscript (Ubuntu)	Fix Released	High	Unassigned
Trusty	Fix Released	High	Unassigned

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.

See original description

Tags:

Related branches

lp:ubuntu/trusty-proposed/ghostscript

Revision history for this message

In Red Hat Bugzilla #1036428, veidea (veidea-redhat-bugs) wrote on 2013-12-01:

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

Revision history for this message

In Red Hat Bugzilla #1036428, Tim (tim-redhat-bugs) wrote on 2013-12-02:

#10

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".

Revision history for this message

In Red Hat Bugzilla #1036428, veidea (veidea-redhat-bugs) wrote on 2013-12-05:

#11

Created attachment 833114
error log

Revision history for this message

In Red Hat Bugzilla #1036428, Tim (tim-redhat-bugs) wrote on 2013-12-05:

#12

Download full text (3.5 KiB)

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=m...

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

Revision history for this message

In Red Hat Bugzilla #1036428, Tim (tim-redhat-bugs) wrote on 2013-12-10:

#13

Created attachment 834836
gs-bisected.patch

'git bisect' shows this to be the fix.

Revision history for this message

In Red Hat Bugzilla #1036428, Fedora (fedora-redhat-bugs) wrote on 2013-12-10:

#14

ghostscript-9.10-5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ghostscript-9.10-5.fc19

Revision history for this message

In Red Hat Bugzilla #1036428, Fedora (fedora-redhat-bugs) wrote on 2013-12-10:

#15

ghostscript-9.10-5.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/ghostscript-9.10-5.fc20

Revision history for this message

In Red Hat Bugzilla #1036428, Fedora (fedora-redhat-bugs) wrote on 2013-12-11:

#16

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).

Revision history for this message

In Red Hat Bugzilla #1036428, Tim (tim-redhat-bugs) wrote on 2013-12-11:

#17

*** Bug 1027425 has been marked as a duplicate of this bug. ***

Revision history for this message

In Red Hat Bugzilla #1036428, Fedora (fedora-redhat-bugs) wrote on 2013-12-20:

#18

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.

Revision history for this message

In Red Hat Bugzilla #1036428, Fedora (fedora-redhat-bugs) wrote on 2014-02-26:

#19

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.

Revision history for this message

Till Kamppeter (till-kamppeter) wrote on 2014-06-26:

Bug is fixed in Ghostscript 9.14 which comes with Utopic, therefore closing as fixed for Utopic. In Trusty (GS 9.10) I can reproduce the bug with the Ghostscript command line of the Red Hat bug report.

Changed in ghostscript (Ubuntu):
status:	New → Fix Released

Revision history for this message

In Red Hat Bugzilla #1036428, Till (till-redhat-bugs) wrote on 2014-06-26:

#20

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.

Revision history for this message

Till Kamppeter (till-kamppeter) wrote on 2014-06-26:

the fix of the following Ghostscript upstream bug fixes also this bug:

http://bugs.ghostscript.com/show_bug.cgi?id=694154

Till Kamppeter (till-kamppeter) on 2014-06-26

description:	updated
Changed in ghostscript (Ubuntu Trusty):
status:	New → In Progress
importance:	Undecided → High
Changed in ghostscript (Ubuntu):
importance:	Undecided → High

Revision history for this message

Till Kamppeter (till-kamppeter) wrote on 2014-06-26:

Uploaded a fixed package to trusty-proposed. As soon as this package gets approved it will be available for testing and instructions for installing it on a Trusty system will get posted here. Please test this package and tell us here whether it solves your problem. Your feedback is required to make the package an official update.

Revision history for this message

zefox (zefox) wrote on 2014-07-01:

error_log Edit (97.5 KiB, text/plain)

Thank you for your quick answer.
I'm waiting for your instructions.

Yesterday I tried again and :
* dmesg :
[ 796.622427] gs[3033]: segfault at ac ip 00007fab4bd36c18 sp
00007fff3a075ed0 error 4 in libgs.so.9.10[7fab4b9b2000+52a000]

* cupsctl --debug-logging", then print a file, then /var/log/cups/error_log in attachment.

Revision history for this message

Chris J Arges (arges) wrote on 2014-07-01: Please test proposed package

Hello zedoc, or anyone else affected,

Accepted ghostscript into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ghostscript/9.10~dfsg-0ubuntu10.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in ghostscript (Ubuntu Trusty):
status:	In Progress → Fix Committed
tags:	added: verification-needed

Revision history for this message

zefox (zefox) wrote on 2014-07-01:

Hi,
When I used sudo apt-get install ghostscript/trusty-proposed, don't know why it removed lubuntu-core and ghostscript-x.
But thank you it works, now I can print !
So ghostscript/9.10~dfsg-0ubuntu10.2 fix this bug.

tags:

added: verification-done
removed: verification-needed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-07-09:

This bug was fixed in the package ghostscript - 9.10~dfsg-0ubuntu10.2

---------------
ghostscript (9.10~dfsg-0ubuntu10.2) trusty-proposed; urgency=low

* debian/patches/020140626-142b12b-null-check-for-icc-profile.patch:
Add NULL checks for ICC profiles (LP: #1334712, Upstream bug #694154).
-- Till Kamppeter <email address hidden> Thu, 26 Jun 2014 20:15:33 +0200

Changed in ghostscript (Ubuntu Trusty):
status:	Fix Committed → Fix Released

Revision history for this message

Chris Halse Rogers (raof) wrote on 2014-07-09: Update Released

The verification of the Stable Release Update for ghostscript has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Bug Watch Updater (bug-watch-updater) on 2017-10-27