624347 - Problem printing emails with attachments from IMAP server, never finishes (Loading content for Printing) Preparing ...

Status: RESOLVED DUPLICATE of bug 565852

(Thunderbird :: General, defect)

Description

[worlds6440]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7

After clicking File->Print... on an email that has attachments (usually greater than 0.4mb) it shows a window saying:
Printing
Title: (Loading content for Printing)
Progress: Preparing...

The first time this is tried it fails to get any further. If you hit the red 'X' on that window and try again it succeeds.

When thunderbird is closed after this problem, the process remains in the task manager and requires it to be killed manually.

Email Server is local network Cyrus IMAP server
Client is set to not syncronise messages

Reproducible: Sometimes

Steps to Reproduce:
1.Select an email that has attachments (on an IMAP server account not set to synchronise messages)
2.click "File" -> "Print..."
3.Window appears saying "(Loading content for Printing)" and fails to go away.
Actual Results:  
Window appears saying "(Loading content for Printing)" and fails to go away, even after 10 minutes waiting.
When Thunderbird is closed, the process remains in the task manager indefinately.

Expected Results:  
It should have shown me the Printer dialog almost instantly

After this bug has been invoked, it causes thunderbird to sometimes be unresponsive when viewing any other emails. The progress wheel on thunderbird spins constantly whilst nothing is being shown.

Only workaround so far is to close thunderbird and use the task manager to kill the process before restarting thunderbird.

Comment 1

[rsx11m]

This looks like bug 529210, which was fixed by bug 565852. This should become visible in the next 3.1.8 update scheduled for early February.

I'm marking your bug as a duplicate, please feel free to reopen if the issue persists after the next update.