Issue 3002

Summary: OO swriter print crashes ghostscript gs 6.51-7 on debian Woody
Product: gsl Reporter: Unknown <non-migrated>
Component: codeAssignee: christof.pintaske
Status: CLOSED FIXED QA Contact: issues@gsl <issues>
Severity: Trivial    
Priority: P4 CC: issues
Version: current   
Target Milestone: next build   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description Unknown 2002-02-04 22:42:03 UTC 
Experinecing problems printing any document containing more than default font in
text editor /usr/OpenOffice.org641/program/swriter. Using gs with driver stp on
Stylus Color 880 with custom ppd from linuxprinting.org.
/usr/OpenOffice.org641/share/psprint/driver/Epson-Stylus_Color_880-stp-ppd.PPD
Gs output:

Error: /undefinedfilename in --.libfile--
Operand stack:
   Symbol    Font        ()
... same errors appear in running gv on printed_to_*.ps file in xsession on screen.

Tracked problem to line in generated postscript file. Problem temporary solved
by shell script with sed call to clean postscript output before sending it to
printer removing all lines with obvious postscript syntax error.
Use command "clnOOpslpr" instead "lpr" in printer configuration tool
/usr/OpenOffice.org641/program/spadmin !

--- Begin cut ---
#!/bin/sh
# /usr/local/bin/clnOOpslpr
# Clean OpenOffice.org641 messy postscript output
sed -e "/^\/ \/[-_A-z0-9]*  psp_definefont$/ d" $1 | lpr
--- End cut ---

Problem temporary solved (hidden). Able to print "normaly".
I wonder how come I am the only one reporting it?
Marko
Comment 1 lsuarezpotts 2002-02-13 22:47:23 UTC 
reassigning to printing project.
Louis
Comment 2 stx123 2002-02-14 00:28:38 UTC 
Reassign issue to owner of selected subcomponent
Comment 3 stx123 2002-02-14 00:28:58 UTC 
Reassign issue to owner of selected subcomponent
Comment 4 christof.pintaske 2002-02-14 08:12:50 UTC 
OOo has a bug when you print Type1 or printer-resident fonts with
Symbol encoding. Pleases use a TrueType Symbol font as a replacement.
The bug will be fixed in the next release
Comment 5 h.ilter 2002-02-22 12:08:00 UTC 
*** Issue 3124 has been marked as a duplicate of this issue. ***
Comment 6 rmano 2002-03-15 09:37:58 UTC 
It seems that build 642 corrected the problem.
Comment 7 h.ilter 2002-03-22 10:19:06 UTC 
*** Issue 3606 has been marked as a duplicate of this issue. ***
Comment 8 christof.pintaske 2002-04-03 16:58:37 UTC 
fixed in 641Dd
Comment 9 philipp.lohmann 2002-04-26 11:11:24 UTC 
*** Issue 3145 has been marked as a duplicate of this issue. ***
Comment 10 michael.ruess 2002-07-29 11:29:00 UTC 
*** Issue 3074 has been marked as a duplicate of this issue. ***
Comment 11 christof.pintaske 2003-04-09 14:04:23 UTC 
closed