Closed
Bug 383210
Opened 18 years ago
Closed 15 years ago
message appears twice in message list
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 414723
People
(Reporter: mikel, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
3.05 KB,
application/octet-stream
|
Details |
Very often (always?) the most recent message in my inbox appears twice in the thread pane. Clicking on either will display the same message body. See http://mikelward.com/screenshots/thunderbird-duplicatesubject.png for a screenshot.
I'm using an IMAP server. The message only appears once on the server. I don't think it happens for folders other than the inbox. It occurs even after compacting all folders. See the attachment for Thunderbird's msf file.
The other interesting things:
- I'm using the vertical view that's new in Thunderbird 2
- I'm sorting by Date descending, but have hidden the Date column
- I've hidden the folder pane header (#folderPaneHeader) in my user chrome
(Sometimes weird things happen when you modify the chrome)
Reporter | ||
Comment 1•18 years ago
|
||
After changing the view, adding the date, or removing the user chrome customization and restarting, the message still twice.
After deleting the msf file and restarting, the message appears once.
Reporter | ||
Comment 2•18 years ago
|
||
I've observed this in other folders. The most recent occurrence was when I movies a message from my Sent folder into my Family folder. The second most recent one appeared duplicated and the one I moved disappeared from both folders.
Comment 3•15 years ago
|
||
Looks problem of Bug 414723(fixed by Tb3.0b3) or Bug 501392(problem even after fix of Bug 414723. fixed by Tb3.0b3). No one seems to have looked into .msf file you attached to this bug when you opened bug...
Closing as DUP of Bug 414723.
If you can produce your problem with Tb3.0b3 or newer, re-open this bug, please.
Updated•15 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•