[regression] gs crashed with SIGSEGV in gs_interpret()

Bug #333429 reported by Duncan Lithgow
90
This bug affects 3 people
Affects Status Importance Assigned to Milestone
GS-GPL
Fix Released
High
ghostscript (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ghostscript

Just added a driver for my Epson Stylus CX3200 using the printer wizard. This bug seems to turn up when I try to run the 'Print Test Page' action.

ProblemType: Crash
Architecture: i386
Disassembly: 0x0:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gs
NonfreeKernelModules: nvidia
Package: ghostscript 8.64.dfsg.1-0ubuntu2
ProcCmdline: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -I/usr/share/cups/fonts -sMediaType=Plain -r720x360 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 -dcupsRowFeed=5 -scupsPageSizeName=A4 -c -f -_
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_DK.UTF8
Signal: 11
SourcePackage: ghostscript
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgs.so.8
 ?? () from /usr/lib/libgs.so.8
 gs_interpret () from /usr/lib/libgs.so.8
 gs_main_run_string_end () from /usr/lib/libgs.so.8
Title: gs crashed with SIGSEGV in gs_interpret()
Uname: Linux 2.6.28-8-generic i686
UserGroups:

Related branches

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
setcolor_cont (i_ctx_p=0x814dc44) at ./psi/zcolor.c:5485
interp (pi_ctx_p=0x81331c4, pref=<value optimized out>,
gs_interpret (pi_ctx_p=0x81331c4, pref=0xbf9744fc,
gs_main_run_string_end (minst=0x8133170, user_errors=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
description: updated
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
setcolor_cont (i_ctx_p=0x814dc44) at ./psi/zcolor.c:5485
interp (pi_ctx_p=0x81331c4, pref=<value optimized out>,
gs_interpret (pi_ctx_p=0x81331c4, pref=0xbf9744fc,
gs_main_run_string_end (minst=0x8133170, user_errors=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Bruce R (bm007a0030) wrote :

This crash report simply arises after StartUp, presumably asd a result of installing my Epson Stylus Photo R220, whose Print Test page doesn't function, but which actually prints from other packages.

Revision history for this message
Serobur (serobur) wrote :

The same as authors, Epson Stylus Photo R340

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

With two others having the same problem with Epson drivers, I'm marking this as confirmed.

Changed in ghostscript (Ubuntu):
status: New → Confirmed
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

This seems to be an upstream bug of Ghostscript 8.64. Reported upstream ...

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

To get some more information about the input data for Ghostscript and the conditions under which the driver is used, please attach the PPD file of your print queue (/etc/cups/ppd/<queue name>.ppd) and do the following:

cancel -a
cupsctl LogLevel=debug

Now print a job and wait until it disappears or goes into "Stopped" state. Then do

sudo cp /var/log/cups/error_log ~
sudo chmod 777 ~/error_log

and attach ~/error_log to this bug report.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

I succeeded to reproduce the bug on 64-bit with the following command line:

cat /usr/share/system-config-printer/testpage-a4.ps | /usr/lib/cups/filter/pstopdf 1 1 1 1 '' | gs -dPARANOIDSAFER -dNOPAUSE -dBATCH -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -I/usr/share/cups/fonts -sMediaType=Plain -r720x360 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 -dcupsRowFeed=5 -scupsPageSizeName=A4 -c -f -_ > output

I get a segfault and the file "output" stays empty.

I have submitted the Apport backtrace as bug #345576 (marked as duplicate of this one).

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

I'm sorry but I won't have access to the cx3200 printer for another three months.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

bug 343171 is possibly the same problem.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Bug fixed upstream. Jaunty fix will come after the beta release.

Changed in ghostscript (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

For testing you can download the package from my PPA:

https://edge.launchpad.net/~till-kamppeter/+archive/ppa

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Corrected version on PPA, please test ghostscript_8.64.dfsg.1-0ubuntu5~ppa1.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

In the duplicate bug 348006 it got confirmed that the fix on my PPA solved the problem.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ghostscript - 8.64.dfsg.1-0ubuntu5

---------------
ghostscript (8.64.dfsg.1-0ubuntu5) jaunty; urgency=low

  * debian/patches/00list: Really apply the patch for LP: #333429.

 -- Till Kamppeter <email address hidden> Wed, 25 Mar 2009 18:32:49 +0100

Changed in ghostscript:
status: In Progress → Fix Released
Revision history for this message
Bruce R (bm007a0030) wrote :

Crash Report generated by merely playing MP3 tracks in Exaile, which was installed instead of the more complex new Amarok.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Bruce R, are you sure that your comment was intended for this bug (Ghostscript)?

Changed in gs-gpl:
status: Unknown → Fix Released
Changed in gs-gpl:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.