Closed Bug 431287 Opened 16 years ago Closed 16 years ago

[Print] Header/Footer is not printed while printing the mail

Categories

(Thunderbird :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: aalam, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008041816 Fedora/3.0-0.55.beta5.fc9 Firefox/3.0b5
Build Identifier: 20080418

Description of problem:
While Printing mail from thunderbird, it shows Header/Footer in "Print Preview",
but not print in actual Print (Hard Copy)

Version-Release number of selected component (if applicable):
thunderbird-2.0.0.12-6.fc9.i386

How reproducible:
Everytime



Reproducible: Always

Steps to Reproduce:
1. run thunderbird
2. print any mail (without any "File->Print Setup")
3.
  
Actual Results:  
Not printing any header

Expected Results:  
should print header as per showing in "Print Prview"

PS file is showing correct field and Printing file, but hard copy Not
Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=444424
This may be the same printable-area issue as in bug 130075.
See bug 407413 comment #3 for a workaround.

If this works, please report back so that we can resolve this bug.
Did you try if the workaround I mentioned in comment #1 resolves this issue?
I also do not see any activity in the Red Hat bug you are referring to.

Please provider further information within two weeks, otherwise this report
will be closed as incomplete.
Whiteboard: closeme 07/10
Whiteboard: closeme 07/10 → closeme 2008-07-10
RESO INCO per last comment due to lack of response to question. If you feel this change was made in error, please respond to this comment with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme 2008-07-10
My impression is that either this bug 130075 (in which case it is a duplicate) or due to some customization that Red Hat / Fedora performed on their end (in which case this bug would be invalid).
You need to log in before you can comment on or make changes to this bug.