Issue 8618 - printing with selected tray increments the tray
Summary: printing with selected tray increments the tray
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: Sun Solaris
: P3 Trivial (vote)
Target Milestone: OOo 1.1 Beta2
Assignee: ulf.stroehler
QA Contact: issues@framework
Depends on:
Reported: 2002-10-22 23:21 UTC by jmills
Modified: 2003-05-20 10:46 UTC (History)
1 user (show)

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

PPD used by user (98.67 KB, text/plain)
2003-04-08 14:23 UTC, philipp.lohmann
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description jmills 2002-10-22 23:21:36 UTC
This is really strange.

I have a file which I print.

for the sake of discussion, we can say it's the same as IZ8617.

we have a Xerox docucolor 40 copier, set up as a colour printer.

If I print to it, select printer properties, and set the tray from autoselect 
to tray 2, the job prints fine.

if I then want another copy, I go "Print" - and the dialog box tells me it has
selected tray 3 to rpint on.

If I click OK, and then print again, it tries tray4!

if I overwrite the tray back to 2, it prints ok.  If I do not, it asks me
to load paper into the tray (eg tray3, then tray4)
Comment 1 frank 2002-10-23 08:46:54 UTC
Wrong Component.

Printing is handled by framework, so I set the flags and reassign it.

Comment 2 thorsten.martens 2002-11-18 11:08:06 UTC
TM->HI: Can you please have a look ? It´s a printing problem, thanks !
Comment 3 h.ilter 2002-11-28 13:54:07 UTC
HI->PL: Unfortunately we haven't such printer. May you have a trick to
Comment 4 philipp.lohmann 2003-01-24 12:56:01 UTC
what PPD do you use ? i did not find a docucolor 40 on Xerxox's site,
just a DocuColor 2006.
Comment 5 philipp.lohmann 2003-04-08 14:21:45 UTC
pl->us: please try to reproduce or close
Comment 6 philipp.lohmann 2003-04-08 14:23:27 UTC
Created attachment 5529 [details]
PPD used by user
Comment 7 ulf.stroehler 2003-04-10 07:49:14 UTC
us->pl: I can reproduce this phenomenon with vcl07, tested on Linux.
Exactly the same way as Jonathan describes with the PPD you attached.
But I was not able to reproduce this with any document. I had to use
the bugdoc Jonathan attached to issue 8617 (as mentioned in the
description). Strange, he?

Note: when starting the vcl07/SWriter the same as when starting
SPadmin I had a warning message in the console:
"Warning: no DefaultResolution in PPD"

This warning message did not show up again after deinstallation of
that "Fiery XP12 Color Server PS" PPD.
Thus again a "buggy" PPD? 
Comment 8 philipp.lohmann 2003-04-10 09:03:58 UTC
I didn't know you needed a special document for this ...
Comment 9 philipp.lohmann 2003-04-10 13:10:57 UTC
The problem was, that with this printer tray 1 is constrained with A3
paper (that is you can not select both smultaneously); since the
application sets the paper size and sometime after that the tray the
unix implementation became confused because at thgat later time fewer
trays were actually allowed; this problem i fixed by numbering all
trays always.

But the problem goes much deeper in principle: the applications do not
set the pagesize on the printer object that is used  in the printer
properties and/or the printer dialogue; this is why the paper size is
always the default paper when you enter the printer setup dialogue (by
pressing "Properties...") and you are able to select tray 1 (please
note that you can't anymore if you change the papersize to A3 in that

This should be worth a followup issue to the applications that they
should set the printer settings of the document before they call the
setup dialogue.

pl->us: would you consider this and file an issue to the applications
if appropriate ?
Comment 10 ulf.stroehler 2003-04-11 09:37:09 UTC
Sounds reasonable to me. Should be feasible in general as the pagesize
should always be known by the applications for e.g. all kind of
formattings and pagelayout.
Will file a follow-up.
Comment 11 philipp.lohmann 2003-04-15 10:03:35 UTC
fixed in vcl08
Comment 12 ulf.stroehler 2003-04-15 15:09:43 UTC
Verified fix.

Filed issue 13459, issue 13461, issue 13462 as follow-ups as PL suggested.
Comment 13 ulf.stroehler 2003-04-15 15:10:20 UTC
Comment 14 thorsten.ziehm 2003-05-20 10:46:34 UTC
Verified in OOo1.1 Beta2.