Bug 85380 - Some (3rd party) fonts won't print
Some (3rd party) fonts won't print
Product: Red Hat Raw Hide
Classification: Retired
Component: openoffice.org (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
Depends On:
  Show dependency treegraph
Reported: 2003-02-28 14:54 EST by Tim Waugh
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-27 11:15:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2003-02-28 14:54:25 EST
Description of problem:
When a document containing one of a few particular fonts (I've found two such
fonts so far) is printed, gs fails with 'Error: /undefined in ...'.

Version-Release number of selected component (if applicable):
Current rawhide (openoffice-1.0.2-4, ghostscript-7.05-32)

How reproducible:

Steps to Reproduce:
1. Fetch the font 'RabbitEars' (google for rabbitears.zip) and install it.
2. Start OpenOffice.org writer, and write something in that font
3. Print it to PS file print.ps
4. gs print.ps

Actual results:
Error: /undefined in RegularHSet1
Operand stack:
   FontName   Hare
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--  
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--  
--nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3  
%oparray_pop   1   3
%oparray_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--
 2   %stopped_push   --nostringval--   --nostringval--   --nostringval--
Dictionary stack:
   --dict:1049/1123(ro)(G)--   --dict:0/20(G)--   --dict:97/200(L)--  
Current allocation mode is local
Current file position is 4931
GNU Ghostscript 7.05: Unrecoverable error, exit code 1

(Could this be a problem with the font itself?)
Comment 1 Dan Williams 2004-02-27 11:15:06 EST
Please try current OOo 1.1.0, and reopen if problem still occurs
Comment 2 Tim Waugh 2004-03-03 08:48:09 EST
1.1.0-28 works.

Note You need to log in before you can comment on or make changes to this bug.