Description of problem:
In the "print setup" dialog box, i have noticed that it states that
"Letter" is the default. Only problem is that i am i Norway, where
letter is only encountered in printer driver setup...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Great and usefull work getting the printer list to work! Will this
find it way back to mozilla/epiphany?
If this is still an issue, please file it upstream. This is something upstream
Mozilla Project should fix.
Is this still an issue in FC4?
Yes. I have a printer which in cups (remote machine) is setup to use "A4", but
when i click on properties for the printer in firefox'es printing dialog, it is
convinced it should produce an Letter postscript...
This does sometimes make advanced printers "hang" - as they do care about which
paper they have, and not have, and so sits there demanding that somebody please
put letter i tray X (or reset it...). Or even worse - they simply fail silently
- the "busy" ligth turns on, turns off (so the data is recived) - and they do
nothing. Very, very difficult to debug.
This is firefox-1.0.4-2 btw.
Please make sure this is filed upstream too. Give the upstream bug URL here.
I really don't want to have yet another bugzilla account to take care of. But it
was already reported:
*** Bug 166105 has been marked as a duplicate of this bug. ***
*** Bug 154545 has been marked as a duplicate of this bug. ***
This is masked at many sites because HP printers have the options Auto Overide
A4=YES* In their settings on the front panel of the printer.
In this instance the printer doesn't care if it gets A4 or Letter it just auto
scales and prints regardless. The feature however available to many masks this
But if this is not the case (or, in the case of old HP laser printers), it will
just refuse to print. Take a look at the two duplicates (and yes, i did report
this bug twice - forgot i reported it once and did it again...)
Sometimes the busy ligth just glows for five secounds, and then nothing happens
- not even an error message. Makes this really really hard to debug...
I agree that it needs fixing, problem is that Fedora people probably
predominately have a US centric view of the world so this stuff doesn't get much
attention. -- I too have the problem with older HP printers ir 4MV Plus and 4Plus.
> Fedora people probably predominately have a US centric view of the world
This might be true to an extent, but keep in mind that the only way this will
get into Fedora is if someone implements it upstream at mozilla.org first.
Great that this was made FC6Target, but it would be great to have it before
then. Firefox is the standard webbrowser in both Fedora and RHEL (as well as a
lot of other distros), and many people depend on it working. I would not be
suprised it is the number one used program on a lot of computers. Having
problems with printing (even if print rendering got much better with 1.5) -
especially problems such as "nothing comes out of the printer, silently" - is
Very Bad. It also causes problems with placement of headers etc.
It has been stated clearly that this is an issue that must be first fixed in
upstream mozilla.org. Fedora will follow upstream, and Fedora tries to stay
away from diverging away from upstream.
(In reply to comment #13)
> It has been stated clearly that this is an issue that must be first fixed in
> upstream mozilla.org. Fedora will follow upstream, and Fedora tries to stay
> away from diverging away from upstream.
Well can't Redhat sponsor the fix and send it upstream.. Sounds like you are
Realistically, I wonder if it's not better as a local fix, as it is dealing with
a locale extension that is primarily only in glibc (LC_PAPER).
Local fix -> a fix to RH source, forgettabout upstream? I'm no expert, but isn't
glibc quite common under linux anyway?
We found that this bug has been already registered in the upstream database
(https://bugzilla.mozilla.org/show_bug.cgi?id=144625) and believe that it is
more appropriate to let it be resolved upstream.
Red Hat will continue to track the issue in the centralized upstream bug
tracker, and will review any bug fixes that become available for consideration
in future updates.
Thank you for the bug report.
*** Bug 186735 has been marked as a duplicate of this bug. ***
*** Bug 445610 has been marked as a duplicate of this bug. ***
The correct upstream bug is: