Printing fails after first page due to gs segfault

Archived topics about LMDE 1
Forum rules
User avatar
mfs
Level 1
Level 1
Posts: 31
Joined: Wed Jul 21, 2010 1:44 pm

Printing fails after first page due to gs segfault

Postby mfs » Thu Nov 24, 2011 4:13 am

Hi,

I've been using LMDE for quite a while now and never had problems with my printer (Kyocera FS 1020D connected to a FritzBox printing server).
But for some weeks now, it's been driving me crazy. When I try to print a PDF the first page (means front and back in duplex mode) is printed, but then the printer tells me that it encountered a "printing error". But in the CUPS error_log (attached) I cannot see anything looking dangerous. However, in the syslog, there is a line reading

Code: Select all

kernel: [ 6793.329576] gs[13646]: segfault at 7fff00000058 ip 00007fc7a9fbb841 sp 00007fffd817c310 error 4 in libgs.so.9.04[7fc7a9e48000+52d000]


I tried the CUPS and gs versions from incoming, debian testing, stable and unstable, but essentially nothing changes - only sometimes the gs segfault in the syslog vanishes, but nevertheless printing fails.

Has anybody an idea what the problem could be?

Thank you for your help,
mfs.

EDIT: These are the versions of CUPS and ghostscript I'm currently using:

Code: Select all

Package cups:                                   
i   1.5.0-12                                      testing,unstable          100
Package cups-bsd:
i A 1.5.0-12                                      testing,unstable          100
Package cups-client:
i A 1.5.0-12                                      testing,unstable          100
Package cups-common:
i A 1.5.0-12                                      testing,unstable          100
Package cups-driver-gutenprint:
i A 5.2.7-2                                       testing,unstable          700
Package cups-pdf:
i A 2.6.1-3                                       testing,unstable          100
Package cups-ppdc:
i A 1.5.0-12                                      testing,unstable          100
Package ghostscript-cups:
i A 9.04~dfsg-2                                   testing,unstable          100
Package libcups2:
i A 1.5.0-12                                      testing,unstable          100
Package libcupscgi1:
i   1.5.0-12                                      testing,unstable          100
Package libcupsdriver1:
i A 1.5.0-12                                      testing,unstable          100
Package libcupsimage2:
i A 1.5.0-12                                      testing,unstable          100
Package libcupsmime1:
i A 1.5.0-12                                      testing,unstable          100
Package libcupsppdc1:
i A 1.5.0-12                                      testing,unstable          100
Package libgnomecups1.0-1:
i A 0.2.3-4                                       testing,unstable          100
Package python-cups:
i   1.9.48-1+b1                                   testing,unstable          700
Package python-cupshelpers:
i   1.2.3-3                                       stable,testing,unstable   700
Package ghostscript:                                   
i A 9.04~dfsg-2                                 testing,unstable           100
Package ghostscript-cups:
i A 9.04~dfsg-2                                 testing,unstable           100
Package ghostscript-x:
i   9.04~dfsg-2                                  testing,unstable           100


EDIT2: I investigated the problem a bit further.The gs segfault showing up in syslog seems to be the cause of the printing problem. When I tail -f syslog and CUPS error_log during printing I see that everything works well until the gs segfault occurs. Then printing stops with the "printer error" (in case I use one of the Foomatic PPDs) or it prints a page that is completely black (in case I use the CUPS+Gutenprint PPD).
Attachments
error_log.tar.bz2
CUPS error_log
(58.25 KiB) Downloaded 35 times

hgrail
Level 1
Level 1
Posts: 3
Joined: Fri Nov 25, 2011 11:22 pm

Re: Printing fails after first page due to gs segfault

Postby hgrail » Sun Jan 01, 2012 8:07 pm

I'm running into the same thing. Has anyone had luck fixing this?


Return to “Archive”

Who is online

Users browsing this forum: No registered users and 3 guests