(/usr/lib/cups/filter/pstopdf) stopped with status 1!

Bug #406925 reported by Quantum
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cups

For weeks I've had this problem, and all my research is for naught. When I try to print from OO or just a regular PDF, I get one blank page rather than however many pages I'd printed.

 The job remains stuck in limbo, and printer status shows "usr/lib/cups/filter/pstopdf failed". In the Cups errorlog is
 E [30/Jul/2009:07:05:50 -0700] PID 15264 (/usr/lib/cups/filter/pstopdf) stopped with status 1!
 E [30/Jul/2009:07:05:59 -0700] [Job 31] Job stopped due to filter errors.

 I found this, which seems to address the exact problem, but unfortunately the final pdftops (downloaded with wget and set to executable) does not help anything:
 https://launchpad.net/bugs/289759

 Setting error level to Debug, this seems like the relevant section:

Code:
  D [30/Jul/2009:07:12:02 -0700] [Job 33] pstopdf argv[6] = 33 root PPM3 - Cascadia - print 1 document-name=te6CES PageSize=Letter InputSlot=Default job-uuid=urn:uuid:5754a9c0-6641-3e84-66e9-af3ee63ca4f9 /var/spool/cups/d00033-001
 D [30/Jul/2009:07:12:02 -0700] [Job 33] PPD: /etc/cups/ppd/lj.ppd
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Resolution:
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Page size: Letter
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Width: 612, height: 792, absolute margins: , , ,
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Relative margins: 18, 36, 18, 36
 D [30/Jul/2009:07:12:02 -0700] [Job 33] PostScript to be injected: <</.HWMargins[18 36 18 36] /Margins[0 0]>>setpagedevice
 D [30/Jul/2009:07:12:02 -0700] [Job 33] PPD options: -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Injecting PostScript: <</.HWMargins[18 36 18 36] /Margins[0 0]>>setpagedevice
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Running cat | /usr/bin/ps2pdf13 -dAutoRotatePages=/None -dAutoFilterColorImages=false -dNOPLATFONTS -dPARANOIDSAFER -sstdout=%stderr -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/printer -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 - -
 D [30/Jul/2009:07:12:02 -0700] [Job 33] GPL Ghostscript SVN PRE-RELEASE 8.64: Set UseCIEColor for UseDeviceIndependentColor to work properly.
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Error: /invalidfont in /findfont
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Operand stack:
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Helvetica-iso1252 --nostringval-- Helvetica Helvetica
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Execution stack:
 D [30/Jul/2009:07:12:02 -0700] [Job 33] %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop 1861 1 3 %oparray_pop 1845 1 3 %oparray_pop 1739 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- 1820 4 3 %oparray_pop
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Dictionary stack:
 D [30/Jul/2009:07:12:02 -0700] [Job 33] --dict:1155/1684(ro)(G)-- --dict:0/20(G)-- --dict:81/200(L)--
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Current allocation mode is local
 D [30/Jul/2009:07:12:02 -0700] [Job 33] Last OS error: 2
 D [30/Jul/2009:07:12:02 -0700] [Job 33] GPL Ghostscript SVN PRE-RELEASE 8.64: Unrecoverable error, exit code 1
 D [30/Jul/2009:07:12:02 -0700] [Job 33] cat: write error: Broken pipe
 D [30/Jul/2009:07:12:02 -0700] [Job 33] cat: write error: Broken pipe
 E [30/Jul/2009:07:12:02 -0700] PID 15645 (/usr/lib/cups/filter/pstopdf) stopped with status 1!
 D [30/Jul/2009:07:12:02 -0700] PID 15646 (/usr/lib/cups/filter/pdftopdf) exited with no errors.

 So it thinks Helvetica is not installed? Beg to differ, in fact I've de/reinstalled it. And shouldn't the font be embedded in the doc anyway, even though I'd created it on this machine?

 This all started a couple weeks ago with the "upgrade" to KDE4. I tried to get the error info according to the Debug page, but my system will not install python-problem-report. (Debian Testing)

 Does anyone have any idea what the problem is? This is now an emergency.

Revision history for this message
Quantum (quantumstate) wrote :

BTW, Cups 1.3.11-1 on a freshly installed Debian Testing system as of two weeks ago. Also had the problem since three months. Please help. I have a critical document I can not print.

Revision history for this message
Quantum (quantumstate) wrote :

OK, I'm dead. I have a 168 page legal document which I MUST get printed and bound right away.

HowTF does a stupid bug crop up like this and survive the ostensible vetting process, to COMPLETELY disable my printing?! Yes I can Force Rasterize and print PDFs, but with this I can not select every other page (as in a book), so it is useless.

I guess I have to resort to Windows and see if I can make -that- work.

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

It looks like a font did not get found by Ghostscript. Can you attach a document with which this problem occurs top this bug report? Thanks.

Can you also try to boot a Ubuntu life CD and see whether you can print out of this environment?

Which version of Ubuntu are you using?

Revision history for this message
Quantum (quantumstate) wrote :

Well this is a highly confidential legal document, and I cannot post it. It used to print, before the Debian "upgrade" two months ago.

 I tried redacting the document of everything except page 1, and now it prints, but all the pages are blank.

I tried printing it on a completely different server (also Debian Testing), but that one gives "Unsupported format application/postscript"!! Unsupported?! Postscript?! No, it's the printing system that is thoroughly busted in Debian all round.

Revision history for this message
Quantum (quantumstate) wrote :

Isn't there anything I can do?

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

We need somehow to reproduce the bug. So we need a file which causes the problem and which is not confidential. Perhaps you create a new file with the application with which you created the confidential file. Which application did you use to create the file which caused the problem?

Changed in cups (Ubuntu):
status: New → Incomplete
Revision history for this message
Quantum (quantumstate) wrote :

Used OpenOffice Writer to create the file, and am using same to try and print, albeit a newer version.

I can email you the file, if you will delete it when finished examining. <email address hidden>

Please, I very much need to print this.

Revision history for this message
Quantum (quantumstate) wrote : Re: [Bug 406925] Re: (/usr/lib/cups/filter/pstopdf) stopped with status 1!
Download full text (5.4 KiB)

Hello Till,

Attached is the file which will not print, as per
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/406925

Please delete this as soon as you've finished troubleshooting.

Best,

Bill Southwell

--- On Fri, 7/31/09, Till Kamppeter <email address hidden> wrote:

> From: Till Kamppeter <email address hidden>
> Subject: [Bug 406925] Re: (/usr/lib/cups/filter/pstopdf) stopped with status 1!
> To: <email address hidden>
> Date: Friday, July 31, 2009, 6:57 AM
> We need somehow to reproduce the bug.
> So we need a file which causes the
> problem and which is not confidential. Perhaps you create a
> new file
> with the application with which you created the
> confidential file. Which
> application did you use to create the file which caused the
> problem?
>
>
> ** Changed in: cups (Ubuntu)
> Status: New =>
> Incomplete
>
> --
> (/usr/lib/cups/filter/pstopdf) stopped with status 1!
> https://bugs.launchpad.net/bugs/406925
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in “cups” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: cups
>
> For weeks I've had this problem, and all my research is for
> naught. When I try to print from OO or just a regular PDF, I
> get one blank page rather than however many pages I'd
> printed.
>
> The job remains stuck in limbo, and printer status shows
> "usr/lib/cups/filter/pstopdf failed". In the Cups errorlog
> is
> E [30/Jul/2009:07:05:50 -0700] PID 15264
> (/usr/lib/cups/filter/pstopdf) stopped with status 1!
> E [30/Jul/2009:07:05:59 -0700] [Job 31] Job stopped due to
> filter errors.
>
> I found this, which seems to address the exact problem,
> but unfortunately the final pdftops (downloaded with wget
> and set to executable) does not help anything:
> https://launchpad.net/bugs/289759
>
> Setting error level to Debug, this seems like the relevant
> section:
>
> Code:
> D [30/Jul/2009:07:12:02 -0700] [Job 33] pstopdf
> argv[6] = 33 root PPM3 - Cascadia - print 1
> document-name=te6CES PageSize=Letter InputSlot=Default
> job-uuid=urn:uuid:5754a9c0-6641-3e84-66e9-af3ee63ca4f9
> /var/spool/cups/d00033-001
> D [30/Jul/2009:07:12:02 -0700] [Job 33] PPD:
> /etc/cups/ppd/lj.ppd
> D [30/Jul/2009:07:12:02 -0700] [Job 33] Resolution:
> D [30/Jul/2009:07:12:02 -0700] [Job 33] Page size: Letter
>
> D [30/Jul/2009:07:12:02 -0700] [Job 33] Width: 612,
> height: 792, absolute margins: , , ,
> D [30/Jul/2009:07:12:02 -0700] [Job 33] Relative margins:
> 18, 36, 18, 36
> D [30/Jul/2009:07:12:02 -0700] [Job 33] PostScript to be
> injected: <</.HWMargins[18 36 18 36] /Margins[0
> 0]>>setpagedevice
> D [30/Jul/2009:07:12:02 -0700] [Job 33] PPD options:
> -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792
> D [30/Jul/2009:07:12:02 -0700] [Job 33] Injecting
> PostScript: <</.HWMargins[18 36 18 36] /Margins[0
> 0]>>setpagedevice
> D [30/Jul/2009:07:12:02 -0700] [Job 33] Running cat |
> /usr/bin/ps2pdf13 -dAutoRotatePages=/None
> -dAutoFilterColorImages=false
> -dNOPLATFONTS -dPARANOIDSAFER
> -sstdout=%stderr -dColorImageFilter=/FlateEncode
>
> -dPDFSETTINGS=...

Read more...

Revision history for this message
Quantum (quantumstate) wrote :

Well I accidentally sent the file to the list. Please delete post 8 and this one.

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

Quantum, I cannot remove comments, but the confidential attachment I have removed now.

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

I have tried to print the files which you have sent me by e-mail. They print correctly on Jaunty and Karmic. I do not have any other version of Ubuntu here.

Which Ubuntu version are you using? According to your error_log it is Intrepid. Am I right?

You can try the following things:

A possible workaround is to export OpenOffice.org documents which do not print directly to PDF (File -> Export to PDF ...). Then print the PDF file from Adobe Reader or Evince.

You should also try to boot from Ubuntu life CDs of Intrepid and later Ubuntu versions. Does it print from Intrepid then? Or from Jaunty?

Revision history for this message
Quantum (quantumstate) wrote :

Actually I am running Debian Testing, which is equivalent to Intrepid.

The only way I can print anything is to export to pdf, and then set Force Rasterize. If I do not force rasterize I get one blank page and nothing more for multiple-page docs.

I'll download Jaunty and try it Live.

Revision history for this message
Quantum (quantumstate) wrote :

Printing another pdf from a completely different source fails also with one blank page, and I get the above error except with the Courier font.

It seems it has no font substitution, or tolerance for fonts for some reason.

Revision history for this message
Quantum (quantumstate) wrote :

I guess no one can figure out what's wrong. All these mission-critical documents are now locked up in a format which is non-printable and unusable. Well I sure hitched my star to the wrong wagon.

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

Did you actually try Jaunty? Does it work there?

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

Arne, this seems to be a font problem. Can you look into it? Thanks.

Revision history for this message
Quantum (quantumstate) wrote :
Download full text (3.7 KiB)

I wondered whether xpdf would give some indication, so I opened a bad pdf file with it, and got:

$ xpdf WorkOrders2539189_082155A.pdf
Warning: Cannot convert string "-*-times-medium-r-normal--16-*-*-*-*-*-iso8859-1" to type FontStruct
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'

This is as my user, and it gives graphics but no text. As root, basically the same thing:

# xpdf WorkOrders2539189_082155A.pdf
Warning: Cannot convert string "-*-times-medium-r-normal--16-*-*-*-*-*-iso8859-1" to type FontStruct
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create a font for 'Courier'
Error: Couldn't create...

Read more...

Revision history for this message
Quantum (quantumstate) wrote :

All right, that's it. Back to Windows for us. I can not have a $60 million contract held up for a stupid software glitch, especially when the developer responsible has lost interest in the project.

This has caused me embarrassment you can not begin to imagine. And is a lost opportunity in finance for open-source which I won't even try to describe.

Congratulations.

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

Quantum, did you try the Jaunty live CD or not?

Revision history for this message
Quantum (quantumstate) wrote :

Yes. When I booted the Jaunty CD I was able to print the problem docs. But I am not going through another complete reinstall on my servers, which takes two days.

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

Either Intrepid bug or user's system configuration broken. Closing ...

Changed in cups (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Quantum (quantumstate) wrote :

Very convenient way to get rid of bugs when you don't know what's wrong.

Revision history for this message
Ben Gamari (bgamari) wrote :
Download full text (3.5 KiB)

This problem (or something very much like it) most certainly still exists on Karmic to this day. Unprintable document attached.

From /var/log/cups/error.log
...
D [05/Sep/2009:10:19:08 -0400] [Job 21] num_components = 1, depth = 8
D [05/Sep/2009:10:19:08 -0400] [Job 21] cupsColorSpace = 0, cupsColorOrder = 0
D [05/Sep/2009:10:19:08 -0400] [Job 21] cupsBitsPerPixel = 8, cupsBitsPerColor = 8
D [05/Sep/2009:10:19:08 -0400] [Job 21] max_gray = 255, dither_grays = 256
D [05/Sep/2009:10:19:08 -0400] [Job 21] max_color = 0, dither_colors = 0
D [05/Sep/2009:10:19:08 -0400] [Job 21] ppd = 0x185b550
D [05/Sep/2009:10:19:08 -0400] [Job 21] PageSize = [ 612.000 792.000 ]
D [05/Sep/2009:10:19:08 -0400] [Job 21] margins = [ -0.000 0.000 0.000 0.000 ]
D [05/Sep/2009:10:19:08 -0400] [Job 21] HWResolution = [ 300.000 300.000 ]
D [05/Sep/2009:10:19:08 -0400] [Job 21] width = 2400, height = 3200
D [05/Sep/2009:10:19:08 -0400] [Job 21] HWMargins = [ 18.000 12.000 18.000 12.000 ]
D [05/Sep/2009:10:19:08 -0400] [Job 21] cups_get_params(0x1689278, 0x7fffa5a7c960)
D [05/Sep/2009:10:19:08 -0400] [Job 21] before gdev_prn_get_params()
D [05/Sep/2009:10:19:08 -0400] [Job 21] after gdev_prn_get_params()
D [05/Sep/2009:10:19:08 -0400] [Job 21] Leaving cups_get_params()
D [05/Sep/2009:10:19:08 -0400] [Job 21] cups_get_params(0x1689278, 0x7fffa5a7c960)
D [05/Sep/2009:10:19:08 -0400] [Job 21] before gdev_prn_get_params()
D [05/Sep/2009:10:19:08 -0400] [Job 21] after gdev_prn_get_params()
D [05/Sep/2009:10:19:08 -0400] [Job 21] Leaving cups_get_params()
D [05/Sep/2009:10:19:08 -0400] [Job 21] Error: /invalidfont in --run--
D [05/Sep/2009:10:19:08 -0400] [Job 21] Operand stack:
D [05/Sep/2009:10:19:08 -0400] [Job 21] (/var/spool/cups/tmp/gs_TFftXz) --nostringval-- --dict:7/16(L)-- R23 1 FontObject --dict:8/8(L)-- --dict:8/8(L)-- 2351 --dict:8/8(L)-- false false --dict:10/11(L)--
D [05/Sep/2009:10:19:08 -0400] [Job 21] Execution stack:
D [05/Sep/2009:10:19:08 -0400] [Job 21] %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop 1861 1 3 %oparray_pop 1845 1 3 %oparray_pop --nostringval-- --nostringval-- --nostringval-- 2 1 9 --nostringval-- %for_pos_int_continue --nostringval-- --nostringval-- false 1 %stopped_push --nostringval-- --nostringval-- --nostringval-- %array_continue --nostringval-- false 1 %stopped_push --nostringval-- %loop_continue --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push --nostringval-- --nostringval-- --nostringval--
D [05/Sep/2009:10:19:08 -0400] [Job 21] Dictionary stack:
D [05/Sep/2009:10:19:08 -0400] [Job 21] --dict:1162/1684(ro)(G)-- --dict:1/20(G)-- --dict:75/200(L)-- --dict:75/200(L)-- --dict:106/127(ro)(G)-- --dict:285/300(ro)(G)-- --dict:22/25(L)-- --dict:4/6(L)-- --dict:21/40(L)-- --dict:1/1(ro)(G)-- --dict:10/15(L)-- --dict:1162/1684(ro)(G)-- --dict:10/1...

Read more...

Revision history for this message
krahim (karim-rahim) wrote :

Hi,

I have a similar problem but it is not a cups problem. I cannot see the attached pdf properly except in acroread.
It does not work with okular, gv, evince, xpdf. I attached the pdf and the output when I try to open the file with xpdf.

I've had this problem since my upgrade to karmic and with several pdf files. I also had troubles with certain websites with firefox and swiftfox and I had to disable allowing pages to use their own fonts.

Warning: Cannot convert string "-*-times-medium-r-normal--16-*-*-*-*-*-iso8859-1" to type FontStruct
Error: Couldn't create a font for 'Helvetica-Bold'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica-Bold'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Symbol'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica-Bold'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica-Bold'

Please find the file attached.

Thanks,
Karim

Revision history for this message
krahim (karim-rahim) wrote :

Note if I open the file in gv I get the following errors or similar errors on each page.

The following error is from the first page.

 Error: /invalidfontGPL Ghostscript 8.70: Unrecoverable error, exit code 1
 in /findfont
Operand stack:
   --dict:5/14(L)-- F6 1 --dict:5/5(L)-- --dict:5/5(L)-- Helvetica-Bold Helvetica-Bold
Execution stack:
   %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop 1861 1 3 %oparray_pop 1845 1 3 %oparray_pop 1739 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- %array_continue --nostringval-- false 1 %stopped_push --nostringval-- %loop_continue --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- 1820 7 8 %oparray_pop
Dictionary stack:
   --dict:1153/1684(ro)(G)-- --dict:1/20(G)-- --dict:75/200(L)-- --dict:106/127(ro)(G)-- --dict:285/300(ro)(G)-- --dict:22/25(L)-- --dict:4/6(L)-- --dict:25/40(L)--
Current allocation mode is local
Last OS error: 2

Thanks
Karim

Revision history for this message
Sam Liddicott (sam-liddicott) wrote :

When I try to print a test-page I get this error:
D [03/Feb/2010:15:04:33 +0000] [Job 4] Error: /invalidfont in /findfont

This is on a freshly installed and up-to-date Karmic as of today.

Revision history for this message
Sam Liddicott (sam-liddicott) wrote :

I think my bug is #321932

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :
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.