gs crashed with SIGSEGV in gx_image_cached_char()

Bug #618798 reported by André Gondim on 2010-08-16
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
GS-GPL
Unknown
Unknown
ghostscript (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: ghostscript

I just tryed to print in network printer.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: ghostscript 8.71.dfsg.2-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Mon Aug 16 15:01:30 2010
ExecutablePath: /usr/bin/gs
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
Lpstat: device for Epson-Stylus-TX105: lpd://192.168.0.1/lp1
MachineType: Dell Inc. Inspiron 1525
Papersize: a4
PpdFiles: Epson-Stylus-TX105: Epson Stylus TX105 - CUPS+Gutenprint v5.2.6 Simplified
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-15-generic root=UUID=15e4dcc6-591c-43f9-803f-cefb3644c4fc ro quiet splash
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=4 -scupsPageSizeName=A4 -c -f -_
ProcEnviron:
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f651a1f6d24: mov %bl,(%r8)
 PC (0x7f651a1f6d24) ok
 source "%bl" ok
 destination "(%r8)" (0x0000023c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: ghostscript
StacktraceTop:
 ?? () from /usr/lib/libgs.so.8
 gx_image_cached_char () from /usr/lib/libgs.so.8
 ?? () from /usr/lib/libgs.so.8
 ?? () from /usr/lib/libgs.so.8
 op_show_continue () from /usr/lib/libgs.so.8
Title: gs crashed with SIGSEGV in gx_image_cached_char()
UserGroups:

dmi.bios.date: 03/10/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/10/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.

André Gondim (andregondim) wrote :
visibility: private → public
Tim Lunn (darkxst) wrote :

same problem here, gs crashes on trying to print to network printer.

job never prints ;(

Till Kamppeter (till-kamppeter) wrote :

Can you all please attach the file(s) which you tried to print and which application and which settings you have used?

Changed in ghostscript (Ubuntu):
status: New → Incomplete
Till Kamppeter (till-kamppeter) wrote :

Can you also make sure that your system is completely updated, especially to exclude that your problem is caused by bug 628030.

  could well be the same bug

running
  cupsctl RIPCache=auto
does fix it.

my system is completely updated (Maverick), what version of cups was this fixed in?

I have Version: 1.4.4-3ubuntu1

On 09/09/10 00:17, Till Kamppeter wrote:
> Can you also make sure that your system is completely updated,
> especially to exclude that your problem is caused by bug 628030.
>

Till Kamppeter (till-kamppeter) wrote :

Yes, CUPS 1.4.4-3ubuntu1 is the version with the fix.

Tim Lunn (darkxst) wrote :

  well then it doesn't appeared to be fixed, since I have to run that cupsctl command manually to get the fix working;(

On 09/09/10 08:44, Till Kamppeter wrote:
> Yes, CUPS 1.4.4-3ubuntu1 is the version with the fix.
>

Till Kamppeter (till-kamppeter) wrote :

Tim, you are sure that the bug occurs when you have CUPS 1.4.4-3ubuntu1 installed and your /etc/cups/cupsd.conf does not contain any RIPCache=... line.

Andre, Tim, can you attach files which (formerly) caused the problem for you? Tell also which applications you used and which settings.

Tim, Andre, note that the most recent update of CUPS sets RIPCache=auto by default if there is no RIPCache line in /etc/cups/cupsd.conf (Remember to restart CUPS with "sudo /etc/init.d/cups restart" after editing cupsd.conf)..

André Gondim (andregondim) wrote :

Hi Till,

Since I have installed Ubuntu 10.10 Maverick Meerkat Beta, in fresh install, this don't happens anymore.

Cheers.

Tim Lunn (darkxst) wrote :

I suppose its possible that I had the old cupsd.conf, however I am 99% certain, I hit replace when the message came up re new config files about a week ago, when cups upgraded.

now I dont have the former file, it appears to have been updated when I ran cupsctl (I did not edit it), and I cant recreate this again. It would appear that there might have been an old RIPcache setting in that file, but is gone now.

Tim, so we can assume that your issue is solved for now?

André, can you attach files which (formerly) caused the problem for you? Tell also which applications you used and which settings. Does the CUPS update solve the problem for you, too?

StacktraceTop:
 mem_true24_copy_mono (dev=<value optimized out>,
 gx_image_cached_char (penum=0x14afae8, cc=0x3f)
 show_update (penum=0x14afae8) at ./base/gxchar.c:833
 show_proceed (penum=0x14afae8)
 ?? ()

Changed in ghostscript (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

The stack trace obtained by Apport looks very similar to the gdb stack trace in

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

which is the upstream report of bug 628030. So this one seems to be a duplicate.

mugginz (mugginz1) wrote :

Still having this issue

It's a clean install of Maverick RC x64

/var/log/cups/error_log contains this
D [06/Oct/2010:16:27:46 +1100] [Job 15] printer-state-message="/usr/lib/cups/filter/pdftoraster failed"

Packages are as follows.

ii cups 1.4.4-6ubuntu2 Common UNIX Printing System(tm) - server
ii cups-bsd 1.4.4-6ubuntu2 Common UNIX Printing System(tm) - BSD comman
ii cups-client 1.4.4-6ubuntu2 Common UNIX Printing System(tm) - client pro
ii cups-common 1.4.4-6ubuntu2 Common UNIX Printing System(tm) - common fil
ii cups-driver-gu 5.2.6-0ubuntu8 printer drivers for CUPS

What's the best way to generate a trace?

mugginz (mugginz1) wrote :

Attached is the output of the printing trouble shooter

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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