Occassionally, a message that is selected to be displayed fails to be displayed, either in the lower pane or in a new window. This is resolved by closing Mozilla, reopening it, and relogging in.



MailNews: Message Display
14 years ago
12 years ago


(Reporter: Ben Rosenau, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)





14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030827

I have multiple accounts logged in at once whenever this happens, however, as I
ALWAYS have multiple accounts logged in, I don't know if this problem is unique
to that or not.  The message always will display fine after restarting as
described in the summary.  Often, one or more messages will be "broken" but
everything else is fine.  What IS displayed in the bottom right pane is whatever
was beforehand, either another message or the opening screen for down there.

Reproducible: Sometimes

Steps to Reproduce:
1. Log in to my e-mail accounts.
2. View an inbox.
3. Click on a message and wait for it to come up (or not) in the bottom right
pane, or double-click the message and wait for the new window that comes up to
display (or not) the message.
Actual Results:  
As above.

Expected Results:  
Shown the message text.

Comment 1

14 years ago
Sound like a corrupted inbox.msf.

Is your mail server an imap server? If so, you can try the steps from bug 216081
comment 1.

[the issue described there is a different one, but yours may have the same cause]


Comment 2

14 years ago

Thanks for the idea.  I did as you suggested late yesterday afternoon, and this
morning the problem has recurred, so I don't think that was it, though.  

Also, I should add that, at least in recent memory now that I think about it,
the problem has only occurred with the second of the 2 accounts I have
configured in the e-mail client.


Comment 3

14 years ago
The bug persists in RC2, as I've now discovered.
Product: Browser → Seamonkey


13 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.