Closed Bug 267660 Opened 20 years ago Closed 20 years ago

sub folders of the inbox unavailable and corrupted after upgrade from 0.8 to 0.9

Categories

(Thunderbird :: General, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: xn--mlform-iua, Assigned: mscott)

References

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2
Build Identifier: Thunderbird 0.9

I have several accounts in Thunderbird. And in 0.9 the access to sub folders of
the inbox is prevented. As a consequense filters doesn't work -- Thunderbird
says it is because it says it hasn't writing access. 

In addition to this, the sub folders are renamed in the following pattern: lots
of the folder gets identical names.

It also seems that new folders are created, though I am not certain about
whether it is new folder or just and old, empty folder that was renamed.

Reproducible: Always
Steps to Reproduce:
1. Start with a working Thunderbird 0.8
2. Quit and install THunderbird 0.9 instead
3. Se the result: corrupted folder and folder access

Actual Results:  
Lost access to folders. Folders got renamed with duplicate names. 

Expected Results:  
Nothing. Everything should have worked as before.
When I go back to Thunderbird 0.8 I get the folders back and working. Except
for one folder that appears to be permanently renamed (or perpaps it is a newly
created folder -- I am not certain about that).
Reporter, what file is used for mail folder file?
Do "Copy Folder Location" of context menu of folder on Thunderbird 0.9, then
past it to text editor such as simpletext.
Directry/subdirectry/file name listing of Mail directry(folder on Mac OS) by
both Finder and "ls -a" at Unix Terminal window will help analysis by developers.

Since this problem seems to relate to characters in folder/file name
(similar bug 267690 on Japanese folder name is also reported), 
please save text file of file listing etc. in UTF-8 then attach to this bug, or
view this bug with caharacter coding of UTF-8 then paste to Comment field of
this bug. 
I think this is is a 'transition' issue. Somehow, Mac OS X users are hit harder
by this problem than Windows users. On Windows, I got duplicate folder listing,
but I can access all the mails. 

Leif, what Wada asked for would help me track down this problem. Perhaps, the
best we can do is to document that non-ASCII folder should be renamed to
ASCII-only names before upgrading to 0.9. 
Depends on: 268219
WADA, what does «what file is used for mail folder file» mean? 

The  affected folders contain non-ASCII letters, most often the letter «å». When
I applied Copy Folder Location to one of the «Odd» folders (se screen shot) I
get this: 

mailbox:/Users/myusername/Library/Thunderbird/Profiles/Default
User/Mail/cb.fxsonet.com/Inbox.sbd/mållagslista

Otherwise I am not very keen on making screen shots of my mail folder available
online. But I have did, anyway. I will upload them as attachments, and perhaps
delete them again when they are not needed anymore.
Actually, I reconsidered. I can send my listings to WADA and  Jungshik Shin
off-zilla, if they wish.
Thank you for sending it over to me, but I couldn't find which folder is
duplicated. What would help (without your privacy compromised) are :

1. Run TB 0.8
2. Make a new folder with an ASCII-only name (say, 'moztest')
3. Add a couple of subfolders under it with non-ASCII letters in their names
4. Move a few emails to each of them
5. Post the result of 'ls -l' of 'moztest' directory
6. Run TB 0.9
7. See what's wrong with folders in 'moztest'
8. Post the result of 'ls -l' of 'moztest' directory
9. Quit TB 0.9 and relaunch it and see what changed to 'moztest'
10. Do steps 7 and 8 again

As I wrote before, I don't think we can do anything here code-wise except for
fixing bug 268219 and releasing 0.9.1 for Mac OS X. Perhaps, you may wait until
0.9.1 release before conducting the test outlined above.
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 267690 has been marked as a duplicate of this bug. ***
Some Japanese people reported to Bugzilla-Japan that the problem did not occur
after fix for bug 268219.
Leif Halvard Silli, has problem been resolved?

By the way, which is appropriate resolution?
"Fixed by patch for bug 268219" is FIXED or DUP of bug 268219? 
Yes, for me the problem seems to be solved.
I should add which version I use now: version 1.0RC1 (20041201)
According to Comment #10, change to VERIFIED/FIXED. 
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: