93026 - Inbox does not display messages

Status: VERIFIED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[AndyR]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010628
BuildID:    2001062823

After a crash, Mail no longer displays the contents of the Inbox (but other
folders are OK.  The "Properties" for the Inbox folder show the character coding
is 'Arabic (IBM-864)'.  Attempts to set it to '(Western (ISO8859-1)' do not work
(clicking OK does not appear to do anything).

Reproducible: Always
Steps to Reproduce:
1. Launch Mail.
2. Inbox (right-pane) is empty.
3. Click View / Folder Character Coding 
   (or right-click Inbox in tree-pane and select Properties)
4. Select Western (ISO-8859-1) and click OK.

Actual Results:  Properties dialog does not dismiss after clicking OK, and the
Character Coding is still set to Arabic.  Contents of Inbox are still not
visible.  (Am proceeding on assumption that problem is related to "character
coding" setting.)

Expected Results:  Properties dialog should have dismissed and "Character
Coding" setting should have have changed to Western (ISO-8859-1).

Running RedHat 7.1 (kernel 2.4.2) on an SMP system with Helix GNOME.

Comment 1

[AndyR]

Tested with latest 0.9.2+ build (ID: 2001072108) and the first time it was
launched as the affected user, was prompted to "compact folders", which I
allowed it to do.  After this, the contents of the Inbox display correctly. 
Changing the "Character coding" from 'Western' to 'Arabic' did not affect the
display of the Inbox contents.

Switched back to the previous version (0.9.2) and the Inbox also displays
correctly, though the "Character coding" was now set to 'Western', and could not
be reset to 'Arabic'.

This suggests to me that the problem was NOT related to the "Character coding"
value, but was some other, unknown strangeness.

Comment 2

[fenella]

Verifying this bug using Linux (2001-07-26-23-0.9.2)

Comment 3

[hacker formerly known as [e-mail]]

*** Bug 170266 has been marked as a duplicate of this bug. ***