"/usr/lib/cups/filter/foomatic-rip failed" (status 9)

Thanks for your report.
Please be more descriptive. Can you print from other applications or does this happen only with the printer test page?
Also attach the output of the printingbug info script as described here: https://wiki.ubuntu.com/PrintingBugInfoScript.
Can you attach your cups error_log with Loglevel debug activated as described here: https://wiki.ubuntu.com/DebuggingPrintingProblems#cupserrorlog

Lars, foomatic-rip is crashing on the Foomatic/pxlmono PPD for the HP LaserJet 1200. What is strange here is that the "renderer command line" output is missing in the log:

               "D [21/Jun/2008:21:06:56 +0100] [Job 13] Inserting PostScript code for CUPS' page accounting",
               'D [21/Jun/2008:21:06:56 +0100] [Job 13]',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] -----------',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] New page: %%Page: 1 1',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] Inserting option code into "PageSetup" section.',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13]',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] Found: %%BeginPageSetup',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] Flushing FIFO.',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13]',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] Starting renderer',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] Starting process "kid3" (generation 1)',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] Starting process "kid4" (generation 2)',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] JCL: \x1b%-12345X@PJL',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] @PJL SET ECONOMODE=OFF',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] @PJL SET BITSPERPIXEL=2',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] @PJL SET RESOLUTION=600',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] @PJL SET DENSITY=3',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] @PJL SET RET=MEDIUM',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] @PJL SET MANUALFEED=OFF',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] <job data> \x1b%-12345X@PJL RESET',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13]',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13]',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13]',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] Closing renderer',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] *** buffer overflow detected ***: HP_LaserJet_1200 terminated',
               'D [21/Jun/2008:21:06:56 +0100] [Job 13] ======= Backtrace: =========',

I can reproduce this bug in intrepid.

Strange thing is: If I install foomatic-filters from source (the exatct same version, retreived via "apt-get source foomatic-filters"), it works fine. If I then reinstall the package itself, it doesn't work again.

Till, do you know what could be causing this?

Lars, you can see build logs for the Ubuntu package here:

https://launchpad.net/ubuntu/intrepid/+source/foomatic-filters/4.0.0~bzr146-0ubuntu1

Click on "Builds" on the left and then click the build link for your architecture. After that click the "Build Log" link on the right. Compare the Ubuntu build with your local build.

There are no patches appied to the foomatic-filters package.

Some data was written over array bounds. The foomatic-filters package doesn't use the default compilation options, that's why I didn't get it on my system (I guess).

The fix is upstream.

On Mon, Jun 23, 2008 at 5:41 PM, Lars Uebernickel
<email address hidden> wrote:
> ** Changed in: foomatic-filters (Ubuntu)
> Status: Confirmed => Fix Committed

Wow, guys. Very swift action on this bug! I don't suppose you still
need the information requested of me by Pascal earlier, do you?

> Wow, guys. Very swift action on this bug! I don't suppose you still
> need the information requested of me by Pascal earlier, do you?

Nope, everything I needed was in the troubleshoot file (it includes the cups_error log and some other useful stuff).

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

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

  * New upstream release (BZR rev 148)
     - Fixed crasher bug (LP: #241979).
     - Eliminate compiler warnings ("-Wall").
     - Allow float values on *OrderDependency settings. This is
       valid according to the PPD spec, and is used by some HP PPDs.
     - Allow choice names starting with "From". Even if they do not
       point to a valid composite option.
     - Parse more complex command lines correctly when looking for
       the "gs" executable to optimize Ghostscript command lines
       for the needs of foomatic-rip.

 -- Till Kamppeter <email address hidden> Tue, 24 Jun 2008 08:25:55 +0200

Tim, thank you for your great troubleshooting tool in system-config-printer! This bug got fixed thanks to your tool. Great is especially that the user found the tool by himself, not like with printing bug info script, where we always need to post the link.

Pascal, what about working together with Tim to get all functionality of the printing bug info script into the trouble shooting tool of system-config-printer?

Glad you find it useful. :-)

Please file enhancement requests here, one by one:

  https://fedorahosted.org/system-config-printer/

and choose 'Troubleshooter' as the component for each.

On Tue, Jun 24, 2008 at 10:04 AM, Till Kamppeter
<email address hidden> wrote:
> Tim, thank you for your great troubleshooting tool in system-config-
> printer! This bug got fixed thanks to your tool. Great is especially
> that the user found the tool by himself, not like with printing bug info
> script, where we always need to post the link.

I must just echo this; I was very impressed, and it worked very well.
Great work, guys!

cvwsaw, are you really sure that your attachment is intended for this bug?