foomatic-rip crashed with SIGSEGV

StacktraceTop:option_get_command (cmd=0x259a460, opt=0x2587e50,
build_commandline (optset=3, cmdline=0x259a410,
render_pages (
print_pdf (s=<value optimized out>,
print_file (filename=0x2584120 "<STDIN>",

Should be fixed in Jaunty in the 4.0.0 final release.

Accepted foomatic-filters into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

This is perhaps solved by the final release of Foomatic 4.0. If you use Jaunty, please do a full update of your system, if you use Intrepid, try the proposed SRU for bug 318818, bug 318816, bug 303691, and bug 299918. To do so, please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Report your results here. Thank you in advance!

Regression caused by foomatic-filters 4.0.0-0ubuntu0.1 from intrepid-proposed, causes all printing to fail on my system, reverting to 4.0.0~bzr177-0ubuntu1 from intrepid restores functionality.

Error log is attached.

Your problem is related to an old-generation (Foomatic 3) PPD file, similar to bug 302935. Please return to foomatic-filters 4.0.0-0ubuntu0.1 and proceed as described here:

Start system-config-printer, right-click the icon for your Brother HL-2060 ("BrotherLaser") and choose "Copy" to make a copy of your print queue, Enter a new name, like "BrotherLaser-debug". Then right-click the "BrotherLaser" again and choose "Properties". You should be in the "Settings" section of the properties dialog. There click the "Change" button in the "Make and Model" line. After loading the driver list system-config-printer lets you choose manufacturer, model, and driver. Go with the default settings by simply clicking "Forward" several times and "Apply" in the end. This should update your PPD. Try to print. It should work now.

Now you have two print queues. Your old one should be in a working state now for daily printing. The new one is a copy of the state of your old queue as it did not work. Use it for the further steps needed to fix this bug.

Can you please also attach your old PPD file (/etc/cups/ppd/BrotherLaser-debug.ppd)?

Carey Underwood, your problem is already reported as bug 321164, so please post your answer to my previous two postings there. Thanks.

Bill Gjestvang, please check whether the update of foomatic-filters in -proposed fixes your segmentation fault problem. Thanks.

I have fixed the problem reported by Carey Underwood now both upstream (BZR rev 196) and for Intrepid. The Intrepid package I have uploaded to -proposed. It contains all fixes of the original SRU plus the fix for Carey's problem. A debdiff between the old and the new SRU (to add the fix of Carey's problem) is attached.

This should be fixed by:

 foomatic-filters (4.0.0-0ubuntu0.2) intrepid-proposed; urgency=low
 .
   * debian/patches/foomatic-rip-segfault-on-jcl-merging.patch: Fixed
     segfault of the JCL merging process on long JCL command lists
     (LP: #321164). This was also reported on the Intrepid SRU
     4.0.0-0ubuntu0.1 in LP: #318614.

Can you please test if this version fixes the crash, and report back here? Thank you!

There is an updated version which fixes a regression:

 foomatic-filters (4.0.0-0ubuntu0.2) intrepid-proposed; urgency=low
 .
   * debian/patches/foomatic-rip-segfault-on-jcl-merging.patch: Fixed
     segfault of the JCL merging process on long JCL command lists
     (LP: #321164). This was also reported on the Intrepid SRU
     4.0.0-0ubuntu0.1 in LP: #318614.

Can you please test this version instead/again, and report back here? Thank you!

Carey Underwood tells in bug 321164 that his problem got fixed by foomatic-filters 4.0.0-0ubuntu0.2.

Till uploaded a new version. Can you please test this again? (Sorry for all the trouble):

 foomatic-filters (4.0.0-0ubuntu3) intrepid-proposed; urgency=low
 .
   * debian/patches/02-foomatic-rip-binary-data-after-pjl-options-corrupted.patch:
     Binary job data got corrupted after reading PJL options from the driver
     output. This should finally fix LP: #318614.
 .
   * debian/patches/foomatic-rip-segfault-on-jcl-merging.patch,
     debian/patches/01-foomatic-rip-segfault-on-jcl-merging.patch: Renamed patch
     to make the patches getting applied in the correct order.

This bug was fixed in the package foomatic-filters - 4.0.0-0ubuntu3

---------------
foomatic-filters (4.0.0-0ubuntu3) intrepid-proposed; urgency=low

  * debian/patches/02-foomatic-rip-binary-data-after-pjl-options-corrupted.patch:
    Binary job data got corrupted after reading PJL options from the driver
    output. This should finally fix LP: #318614.

  * debian/patches/foomatic-rip-segfault-on-jcl-merging.patch,
    debian/patches/01-foomatic-rip-segfault-on-jcl-merging.patch: Renamed patch
    to make the patches getting applied in the correct order.

 -- Till Kamppeter <email address hidden> Mon, 2 Feb 2009 19:18:49 +0100