Issue 18021 - Unable to hardcopy first-page of text documents
Summary: Unable to hardcopy first-page of text documents
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: caolanm
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-08 11:50 UTC by Unknown
Modified: 2003-09-12 11:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-08-08 11:50:30 UTC 
Hardware: Toshiba 7220 Crt, 128MB, RAM
OS: Redhat 9, kernel 2.4.21, Xfree86 v4.3.0-2

If I try to print any text document to file or printer, the postscript file
produced can be displayed correctly using ghostscript. However, when sending to
the printer, the first page is produced but blank. Subsequent pages are printed
correctly.

All printers are currently configured using the OO supplied SGENPRT.PS psprint
driver.
Comment 1 philipp.lohmann 2003-08-08 13:37:39 UTC 
What kind of printer do you use ?
Comment 2 Unknown 2003-08-09 21:45:07 UTC 
I'm printing to a HP LJ8000DN via smbclient and/or cups.

Problem now seems to be limited to imported documents from MS Word
2000. Native documents (.sdw) and others seem to be unaffected by this
issue.
Comment 3 christof.pintaske 2003-09-01 14:13:51 UTC 
please provide an according sample document for evaluation
Comment 4 christof.pintaske 2003-09-08 11:57:35 UTC 
caolan, seems to affect imported documents only. do you have an idea
about this one ? any chance to reproduce ?
Comment 5 Unknown 2003-09-09 09:13:32 UTC 
False alarm I'm afraid.

Buried in the printer driver was a call to "mpage" which seems to be
the root of this issue. Changing printer and spooling directly has no
problems... All I need to do now is find a replacement for the
duplexing functionality.

Thanks for checking this out anyway
Comment 6 caolanm 2003-09-09 09:16:07 UTC 
Was there any reason that it happened with word2000 and not native
document, or was that a pure coincidence ?
Comment 7 caolanm 2003-09-12 11:56:53 UTC 
Oky doky, I'll close this then