Bug 456351 - Only the last message is printed when printing multi-messages to file
Only the last message is printed when printing multi-messages to file
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: thunderbird (Show other bugs)
5.2
x86_64 Linux
low Severity low
: rc
: ---
Assigned To: Martin Stransky
desktop-bugs@redhat.com
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-22 22:31 EDT by Yolkfull Chow
Modified: 2017-04-04 16:43 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-04-04 16:43:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
example (29.35 KB, application/pdf)
2009-03-11 12:34 EDT, Matěj Cepl
no flags Details

  None (edit)
Description Yolkfull Chow 2008-07-22 22:31:00 EDT
Description of problem:
When select multiple messages and print them to file, only the last message has
been printed into the file.

Version-Release number of selected component (if applicable):
thunderbird-2.0.0.16-1.el5

How reproducible:
Always

Steps to Reproduce:
1. select multiple messages
2. print the selected messages to a file
3. open the file
  
Actual results:
only the last message has been printed

Expected results:
all the selected messages should be printed to the file

Additional info:
Does it relate to bug #201314?
Comment 1 lihuang 2008-07-23 04:03:00 EDT
Reproduced this problem with thunderbird-1.5.0.12-14.el4.i386 &
thunderbird-1.5.0.12-14..el4.x86_64
Comment 2 Matěj Cepl 2008-07-25 07:17:31 EDT
Yes, can fully reproduce with thunderbird-2.0.0.16-1.el5. It looks like if TB
prints out every message to the same file and so rewriting their contents.
Comment 3 Matěj Cepl 2009-03-11 12:29:10 EDT
*** Bug 489530 has been marked as a duplicate of this bug. ***
Comment 4 Matěj Cepl 2009-03-11 12:34:34 EDT
Created attachment 334833 [details]
example

Can reproduce with TB 3.0beta on Rawhide
Comment 5 Jonathan Kamens 2009-03-11 12:35:41 EDT
Please note that the description of this bug and the description of the behavior I saw in bug 489530 are different.

Please note also that this ticket is for RHEL 5 and bug 489530 is for Fedora, and they have different versions of thunderbird (and are likely to have different versions of thunderbird for a while), so I'm not convinced that it's appropriate to merge the two bugs.
Comment 6 Jonathan Kamens 2009-03-15 00:41:10 EDT
Hello?  Anybody here?  My last comment is significant, eh?  Can somebody please respond?
Comment 8 Martin Stransky 2015-06-03 08:21:08 EDT
We don't have fix for this issue.
Comment 9 Chris Williams 2017-04-04 16:43:46 EDT
Red Hat Enterprise Linux 5 shipped it's last minor release, 5.11, on September 14th, 2014. On March 31st, 2017 RHEL 5 exits Production Phase 3 and enters Extended Life Phase. For RHEL releases in the Extended Life Phase, Red Hat  will provide limited ongoing technical support. No bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only.  If the customer purchases the Extended Life-cycle Support (ELS), certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release will be provided.  The specific support and services provided during each phase are described in detail at http://redhat.com/rhel/lifecycle

This BZ does not appear to meet ELS criteria so is being closed WONTFIX. If this BZ is critical for your environment and you have an Extended Life-cycle Support Add-on entitlement, please open a case in the Red Hat Customer Portal, https://access.redhat.com ,provide a thorough business justification and ask that the BZ be re-opened for consideration of an errata. Please note, only certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release can be considered.

Note You need to log in before you can comment on or make changes to this bug.