gs crashed with SIGSEGV in cmd_put_list_op()

Bug #859630 reported by urbaman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ghostscript (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Trying to print pdf files

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ghostscript 9.01~dfsg-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 26 14:59:02 2011
ExecutablePath: /usr/bin/gs
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Lpstat: device for HP-Officejet-4500-G510g-m: hp:/net/Officejet_4500_G510g-m?zc=HP7390A4
MachineType: System manufacturer System Product Name
Papersize: a4
PpdFiles: HP-Officejet-4500-G510g-m: HP Officejet 4500 g510g-m, hpcups 3.11.1
ProcCmdline: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOMEDIAATTRS -sDEVICE=cups -sstdout=%stderr -sOUTPUTFILE=%stdout -c -f -_
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=0b11ad88-9163-4cbe-9743-6badbe8adc9a ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fca4134c93f <cmd_put_list_op+191>: mov %rdx,(%rcx)
 PC (0x7fca4134c93f) ok
 source "%rdx" ok
 destination "(%rcx)" (0x690000005b000000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: ghostscript
StacktraceTop:
 cmd_put_list_op () from /usr/lib/libgs.so.9
 cmd_write_unknown () from /usr/lib/libgs.so.9
 clist_stroke_path () from /usr/lib/libgs.so.9
 gx_stroke_fill () from /usr/lib/libgs.so.9
 gs_stroke () from /usr/lib/libgs.so.9
Title: gs crashed with SIGSEGV in cmd_put_list_op()
UpgradeStatus: Upgraded to natty on 2011-04-30 (149 days ago)
UserGroups:

dmi.bios.date: 02/24/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6TD DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd02/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
urbaman (urbaman) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 cmd_put_list_op (cldev=0x7fca41d75068, pcl=0x7fca39f4b598, size=28) at ./base/gxclutil.c:322
 cmd_write_unknown (cldev=0x7fca41d75068, pcls=0x7fca39f4b3e0, must_know=<optimized out>) at ./base/gxclpath.c:479
 clist_stroke_path (dev=0x7fca41d75068, pis=0xeda058, ppath=0xef6858, params=0x7fffd3902ff0, pdcolor=0x15b4fa8, pcpath=0x15b4dd0) at ./base/gxclpath.c:907
 gx_stroke_fill (ppath=0xef6858, pgs=0xeda058) at ./base/gxpaint.c:65
 do_stroke (pgs=0xeda058) at ./base/gspaint.c:431

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ghostscript (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can you attach the PDF file(s) which you tried to print? Can you follow the instructions in the section "Capturing print job data" and "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems? Can you boot from a live CD of Oneiric to see whether the problem persists in Oneiric?

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

From the error_log I can see that you are printing using the Adobe Reader. As a quick workaround try using evince (Document Viewer) instead of Adobe Reader. Evince starts also faster and is faster rendering the pages on the screen. The printing problems which evince had in former Ubuntu versions are fixed.

I have tried to reproduce the bug. I can print your attached PDF file (comment #7) without problems on Natty and Oneiric with both evince and Adobe Reader on two HP inkjets using the hpcups driver (this is exactly your configuration). My error_log shows the same filter path as yours. I get no segmentation faults by these tests. The two test machines are both x86_64.

If I send your captured print data (comment #6, it is a PostScript file as Adobe Reader sends PostScript) to the print queues on the Oneiric box I also get a correct printout, if I send it to a queue on the Natty box I get the crash and the crash in my error_log looks like yours.

One can conclude the following:

- In Oneiric the problem in Ghostscript is fixed.

- The Adobe Reader on my Natty box is probably not the same version as the one on yours. My Adobe Reader is from the official Ubuntu package (partners download source repository). If yours is also from Ubuntu, make sure that your system is fully updated.

- With evince you will not have the problem.

Marking as fixed as Oneiric works. In addition, there is a workaround for Natty (evince).

Changed in ghostscript (Ubuntu):
status: Incomplete → Fix Released
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.