1292170 - Folder email contents not shown in message preview tab after imap folder move. Message does display in full window

Status: RESOLVED DUPLICATE of bug 1328814

(Thunderbird :: Message Reader UI, defect)

Description

[info]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID: 20160726073904

Steps to reproduce:

1. When I click on a folder, the contents of any email in this folder is shown in the preview pane, after clicking on this email.

2. After I move any folder to a new target location (IMAP folders) I can not preview any email in any folder in the preview pane
3. After a restart of Thunderbird the behaviour is back to normal.


Actual results:

All emails can not be previewed in the preview pane after any folder move.


Expected results:

All emails should be previewable even after a folder move.

Comment 1

[Wayne Mery (:wsmwk)]

When did this start happening?
What changed in Thunderbird at around the same time?
Does problem go away if you start Thunderbird in safe mode?
 see https://support.mozilla.org/en-US/kb/safe-mode

Comment 2

[info]

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #1)
> When did this start happening?
Since I use Thunderbird, actual version unclear, but at least at version 35. The error was not really solidified, but with the newest version very reproducible. Clearly connected to a folder move. Clearly dissapears after a restart.

> What changed in Thunderbird at around the same time?
Does not apply.
> Does problem go away if you start Thunderbird in safe mode?
Initially yes because of the restart, but then also persists in safe mode with all add ons disabled.
>  see https://support.mozilla.org/en-US/kb/safe-mode

It only affects the preview pane. By doubleclicking I still can see the email contents. But the preview pane remains empty after a folder move. If I move the folder back to the original location I can view the emails in preview again. After a restart of Thunderbird also.

Comment 3

[Wayne Mery (:wsmwk)]

info,
Please open tools | error console and clear the contents. move a folder and then click a message. what do you see in the error console?

Comment 4

[info]

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #3)
> info,
> Please open tools | error console and clear the contents. move a folder and
> then click a message. what do you see in the error console?

By the way, if I move the folder back to its original location, no additional error message. And then the folder content emails would reappear in the preview pane.

In any case, folder contents appear in a new window, but not in preview pane. So new window always works, but preview should work as well.

Am 11.09.2016 um 03:10 schrieb Frank Dittrich:
>
> Zeitstempel: 11.09.2016 03:05:03
> Fehler: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBHdr.messageId]
> Quelldatei: resource:///modules/WinSearchIntegration.js
> Zeile: 747
>
> Zeitstempel: 11.09.2016 03:05:04
> Fehler: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBHdr.messageId]
> Quelldatei: resource:///modules/WinSearchIntegration.js
> Zeile: 747
>
> Zeitstempel: 11.09.2016 03:05:10
> Fehler: 2016-09-11 03:05:10    gloda.index_msg    ERROR    Exception while attempting to mark message with gloda state afterdb commit [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBHdr.getUint32Property]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: resource:///modules/gloda/index_msg.js :: PendingCommitTracker_commitCallback :: line 161"  data: no]
>
> Quelldatei: resource:///modules/gloda/log4moz.js
> Zeile: 691
>
> So 3 error messages directly after the folder move, no idea what it means.
>
> Thanks for your analysis Wayne, since this is bothering me constantly over different versions and reinstalls, on different computers.

Comment 5

[info]

Anyone working on this?

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to info from comment #5)
> Anyone working on this?

not so far. All the activity that would have happened is logged in the bug report

Comment 7

[Wayne Mery (:wsmwk)]

This matches the symptoms of bug 1120361.
No need to comment there - I think we have all the information needed to make progress.

Comment 9

[WADA:World Anti-bad-Duping Agency]

Cause of problem was found at last, and bug 1328814 was opened.