foomatic-rip crashed with SIGSEGV in strlen()

Bug #260211 reported by darkenergy
20
Affects Status Importance Assigned to Milestone
foomatic-filters (Ubuntu)
Fix Released
Medium
Lars Karlitski

Bug Description

Binary package hint: foomatic-filters

every print job crashes after beeing ALMOST correctly printed
(the pages are all missing their footer line with page numer and file name)

tested with open office and a from there exported pdf

Printer: HP Photosmart C4280
Ubuntu Intrepid Ibex

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/foomatic-rip
Package: foomatic-filters 4.0.0~bzr160-0ubuntu1
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: Photosmart-C4200-series 1 dominik Synthese\ von\ cis-Cyclohexan-1,2-diol_final_corrected_2 1 PageSize=A4\ InputSlot=Default\ job-uuid=urn:uuid:5b1812fe-5849-32e4-7e6a-1e593903f3b3
ProcEnviron:
 PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin
 LANG=de_CH.UTF8
Signal: 11
SourcePackage: foomatic-filters
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 vfprintf () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 vfprintf () from /lib/tls/i686/cmov/libc.so.6
 __vfprintf_chk () from /lib/tls/i686/cmov/libc.so.6
Title: foomatic-rip crashed with SIGSEGV in strlen()
Uname: Linux 2.6.26-5-generic i686
UserGroups:

Tags: apport-crash
Revision history for this message
darkenergy (darkenergy) wrote :
Changed in foomatic-filters:
assignee: nobody → larsuebernickel
importance: Undecided → Medium
Revision history for this message
Lars Karlitski (larsu) wrote :

Thanks for reporting this bug. Unfortunately, I cannot reproduce it. Could you please attach the exact PPD you are using (/etc/cups/ppd/<printername>.ppd) and the cups error log (/var/log/cups/error_log). The error log is most useful if the log level is set to debug (set "LogLevel" in /etc/cups/cupsd.conf to "debug").

Changed in foomatic-filters:
status: New → Incomplete
Revision history for this message
darkenergy (darkenergy) wrote :
Revision history for this message
darkenergy (darkenergy) wrote :
Revision history for this message
darkenergy (darkenergy) wrote :
Revision history for this message
darkenergy (darkenergy) wrote :

so - i hope that's enough information for the moment.

I like to help, whenever i can (that's why I'm using an alpha)

Revision history for this message
Salih EMIN (salih-emin) wrote :

every print job crashes after beeing CORRECTLY printed
the pages are all OK with page numer and file name. The file I printed was a .pdf opened with Evince 2.23.6.

Revision history for this message
darkenergy (darkenergy) wrote :

update from my part:
the pages are now also printed "correctly" (optically) but not technically. there is still the same crash as reported after every job. (the job is then kept in the list and set "stopped")

i think the past cups updates fixed the problem with the missing footer reported earlier.

hope the files added last time are enough to triage this bug.

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

This bug is caused by the following upstream bug:

http://bugs.linux-foundation.org/show_bug.cgi?id=160

The bug is fixed upstream and a fixed foomatic-filters package is on its way.

Changed in foomatic-filters:
status: Incomplete → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package foomatic-filters - 4.0.0~bzr164-0ubuntu1

---------------
foomatic-filters (4.0.0~bzr164-0ubuntu1) intrepid; urgency=low

  * New upstream release (BZR rev 164)
     - Fixed bug in building the renderer command line (Upstream bug #160,
       LP: #260211)
     - Fixed crasher bug LP: #259622
     - Partially fixed problem of options submitted with print jobs not being
       obeyed by foomatic-rip (PJL/JCL options still TODO, upstream bug #159).

 -- Till Kamppeter <email address hidden> Tue, 02 Sep 2008 11:29:29 +0200

Changed in foomatic-filters:
status: In Progress → 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.