111852 - UNIX-PS PRINTING: COMPLETLY BROKEN!!!

Status: VERIFIED WORKSFORME

(Core :: Printing: Output, defect)

Description

[Tobias Burnus]

If I use Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:0.9.6+) Gecko/20011117 I
cannot print anymore.

The print dialog shows only an empty combo box for the printers and next to it a
[Properties] button which I cannot use (probably because there is no printer
found :-(

Expected:
a) I can enter the command for printing!!!!
   per example "psnup -2 | lpr -Pfoo -Zsduplex,top,staple" 
   or "lpr -Pprint@foobar"
   (the -Z syntax is LPRng syntax, the print@foobar works
    in LPRng without having the printer in any local configuration)

b) I do like the idea to have the possibility to use simply select the printer
(if you can still enter the command), but this is not that easy:
LPR:    read /etc/printcap
CUPS:   Query the server
XPRINT: Dito
LPRng:  Read /etc/lpd.conf to find out which file to read

c) I need some place to tell Mozilla to use A4 or A3 format. Also for printing
to file, I CANNOT do so any more (letter is wider so some information is cut off)

d) I need to tell mozilla whether I want to use LANDSCAPE or PORTRAIT. I CANNOT
DO SO ANY MORE. NOT EVEN FOR PRINT TO FILE (some big tables only print on landscape)

Comment 1

[Tobias Burnus]

Adding Roland the XPrint specialist who created the nice printing dialog (bug
84947) which misses
- the command input (besides selecting the printer)
- a methode to set the landscape/portrait mode for print to file and for print
via command
- a methode to set the paperformat for print to file and for print via command

Wish:
- Read /etc/printcap and use it as fill-in (for lpr)

(Yes, I know that XPRINT is nice, but CUPS are also nice [are they supported?],
furthermore lpr is still the default under UNIX. Plus I cannot change the use of
LPRng used in my faculty (besides that using a simple "lpr
-Pprinter@a_windows_pc" is nice ;-)

Comment 2

[Bradley Baetz (:bbaetz)]

This isn't a blocker.

Theres a 'properties' button next to the printer selection, where you can set
all this stuff...

Comment 3

[Roland Mainz]

tobias:
Available printers go into the MOZILLA_PRINTER_LIST env. var.
Try
% export MOZILLA_PRINTER_LIST="printer1 printer2@foobar printer3"

I am going to implement per-printer-name prefs soon...

Comment 4

[Roland Mainz]

Looking at the code again... I suspect there may be an issue.
What does
% echo $SHELL
say on your box ?

Comment 5

[R.K.Aa.]

If reporter informs about correct build ID, he is testing a build made 4 days
before the final patch in bug 84947 was checked in.

Comment 6

[Boris Zbarsky [:bzbarsky]]

Tobias, are you building or using a nightly?  I saw this problem in an opt cvs
build until I deleted component.reg....

Comment 7

[R.K.Aa.]

Perhaps this bug is clairvoiant. To add to the confusion, my CVS build (linux)
now only gives error when clicking 'properties' button:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)
[nsIPrintOptions.displayJobProperties]"  nsresult: "0x80040154
(NS_ERROR_FACTORY_NOT_REGISTERED)"  location: "JS frame ::
chrome://global/content/printdialog.js :: displayPropertiesDialog :: line 185" 
data: no]

Comment 8

[Roland Mainz]

R.K.Aa wrote:
> Perhaps this bug is clairvoiant.

clairvoiant=??

> To add to the confusion, my CVS build (linux)
> now only gives error when clicking 'properties' button:

Please wipe-out your whole tree, source, objdir and component.reg and rebuild
from scratch. We changed some interfaces and it looks the XPCOM stuff gets nuts
somehow... ;-(

Comment 9

[rods (gone)]

Roland can you help with this?

Comment 10

[Roland Mainz]

rods:
I assume this bug is ripe for getting marked as "INVALID", isn't it ?
My suggestion is to wipe-out src&objdir and build the Zilla from scratch - or at
least remove component.reg and then check if the problem still exists...

Comment 11

[Roland Mainz]

I tested a 2001-11-24-08-trunk Solaris 7 SPARC GTK+ build using PostScript
module printing http://www.heise.de/ - raw after compiling, no special setup.
WorkForMe...

Comment 12

[R.K.Aa.]

Deleted all in dist and rebuilt from CVS: All is well on Linux.
Still doesn't explain why 20011117 has an error of course.

Comment 13

[rods (gone)]

Seems to work marking work for me per other comments

Comment 14

[sujay]

Tobias, is this workign for you ? please mark this bug VERIFIED-FIXED
if it is...thanks.

Comment 15

[sujay]

verified.

Comment 16

[Eric Vaandering (no email)]

I've opened bug 135695 on the /etc/printcap issue.