304169 - Selecting message does not populate message pane, unless another folder was opened first.

Status: RESOLVED DUPLICATE of bug 312938

(Thunderbird :: Mail Window Front End, defect)

Description

[Eric]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Upon opening Thunderbird, the Inbox of the first account is selected, and the
"Welcome to TBird" is shown in the message pane.  However, single clicking any
of the messages in the message list pane does nothing.  However, if I move to a
different folder, and then back to the Inbox, clicking a message works fine.

This happens whether I set the welcome page to blank or the default.

Currently using today's nightly build (version 1.0+ (20050810)), installed via
the auto-updater.   I've been seeing this for a few weeks, but I suspected a
problem on my end since I haven't seen anyone else file a bug.  But maybe
they've all been thinking the same thing...

Reproducible: Sometimes

Steps to Reproduce:
1. Start Thunderbird
2. Click a message in the message list pane

Actual Results:  
Nothing happens in the message pane.  The message does become selected in the
message list pane.

Expected Results:  
The message body should be shown in the preview pane.

I had this problem every time I opened Thunderbird up until today - now it's
intermittent.  I'll follow this bug up if I can find some common factor for the
times in which it works properly.

Also, I have six POP3s accounts, a newsgroup account, and 8 RSS feeds, which are
all being checked on startup.  Perhaps there is a problem with viewing messages
in one Inbox while another profile is still downloading messages?

Comment 1

[Adam Guthrie]

Can you reproduce this when you start in safe mode?
http://kb.mozillazine.org/Safe_mode

Comment 2

[Eric]

Well, oddly, I haven't been able to reproduce it at all, safe mode or otherwise,
since I filed this bug.  This is despite the fact that I was definitely able to
reproduce on the same build (yesterday's nightly) at that time.

The only thing I did that was unusual was turn the message pane off and then
back on (F8) while filing this bug.  Ever since I did that, I haven't seen a
problem.

Incidentally, I have no extensions or themes installed for TBird, except for
Talkback.

Perhaps I should WFM this bug?  Or does the F8 link imply something else that
needs attention?

Comment 3

[Adam Guthrie]

Please re-open if you can reproduce.

Comment 4

[Eric]

Well, it's been happening again.  Still no determination of exact steps for
reproducing, unfortunately.  Perhaps it has something to do with receipt of both
normal and Junk messages in the same session, but I haven't been able to test
too much yet.

I can tell you that it happens regardless of whether I click a message or use
the spacebar to advance to the next unread message in the Inbox.  As before, the
message subject/date/etc line becomes highlighted, but the message pane retains
the Welcome page.  Can't say for sure (yet) whether the message is marked Read
or not - I'll make a point to notice this next time it happens.

Now using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4)
Gecko/20050814 Thunderbird/1.0+ ID:2005081406
No themes installed.
Talkback and Nightly Tester extensions installed.

Comment 5

[Eric]

I'm pretty sure that this problem only shows up when some messages are
downloaded, placed in the Inbox, automatically marked as Junk when all messages
are done downloading, and moved out of the Inbox (to a folder on Local Folders).
 After that move happens, clicking other messages in the Inbox has no effect. 
If I click messages before the Junk move happens, I don't see the bug (although
it might just be that I'm getting lucky and the bug wouldn't have happened just
then anyway.)

I also tested whether clicking Unread messages while in bug-mode marks them as
read - it does not.
Nothing in the Javascript Console.
Alt-tabbing, minimizing, maximizing, and opening other dialogs (tools/options,
etc) has no effect - once stuck, it stays stuck unless TBird is restarted, a
message is double-clicked into a new window, or another folder is opened first.

Some configuration information that might be relevant:
All accounts have Junk Filters enabled.
All accounts use their own Inboxes, rather than one shared Inbox.
All accounts move their junk to the same folder on Local Folders.
The last message received as part of the download session that triggered this
bug matched both the Junk filter and a regular message filter.

It appears that Junk is cleared from the primary Inbox multiple times - both
when other accounts are done downloading, and again when the primary account is
done downloading.  The reason I mention this is that my setup has had other
problems with Junk in the distant past (bug 218433), although that might not
have any bearing on the current problem.

Comment 6

[Eric]

Another followup: If the bug is in effect, and more mail is downloaded, the Junk
filter will fail to process the Inbox, but it appears that regular message
filters work just fine.  Mail that would otherwise have been marked junk and
filed remains there until junk filters are manually run (after performing one of
the work arounds).  Haven't tested whether a manual run would work before doing
the workaround.

Comment 7

[Eric]

It does not appear that I have to wait for junk mail controls to apply to the
Inbox for the problem to show up.  During a download session, I tried to look at
some messages before all had been downloaded, and was unable to do so.

Comment 8

[Eric]

Sorry for the spam, but it also appears that double-clicking the message does
not restore normal functionality to the Inbox.  I have to go to another folder
and back.

Comment 9

[Mike Cowperthwaite]

See bug 312938 -- does the step mentioned there for causing the problem consistently also work for you?  If so, please mark this bug as a duplicate of that one.

Comment 10

[Mike Cowperthwaite]

No response from reporter, duping.

*** This bug has been marked as a duplicate of 312938 ***