Closed
Bug 301948
Opened 19 years ago
Closed 19 years ago
mail folder contents wont display unles I try many times
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 300749
People
(Reporter: mnemo, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 when I select the ANTLR mailing list folder (among local folders) its contents display, but later when I select another folder, say BLAH, the ANTLR contents/mails stay. If I at this point select any other folder and then reselect folder BLAH I see its proper contents directly. So the problem occurs ONLY if I had previously viewed the ANTLR contents/mails. Obviously something is wrong with the ANTLR folder, but I don't know what is is. Actually its not just the ANTLR folder but also the Harmony folder and the OpenBEOS/Haiku folder. It shows the same problems, if I select the harmony folder its mails show but then when I select some other folder the mails pane still shows harmony mails (until I click inbox or whatever and the reselect the folder I actually wanted to see). since I suspect that its a problem with these specific folders you might wanna have a look at them (usually, they are a subdir of local folders): http://mnemo.minimum.se/bugged_mozilla_folders/folders.zip now, i did have one problem which could have caused this corrupted folders problem. i tried to create a folder called "java" and the folder was created but the input-new-folder-name reappeared for some mystical reason (not diskspace issue though). im just speculating here, but suppose the folder creation process is like like doSomethingA(); doSomethingB(); and what if the second part failed. maybe there was not a proper cleanup made? that code is my guess for the culprit here. ps. I dont have any problems with lack of diskspace and I have not had such problems in the last few months either. the problems started when I upgraded from 1.7.2 (or was it 1.7.3 perhaps) to 1.7.10 ps. im so tired right now, sorry for the bad english and the lazy formatting. i've been up way to many hours, and my wireless keyboard doesnt work right so it ignores every third key -- which makes typing a pain. Reproducible: Always Steps to Reproduce: 1. see above for reprod, but you need mail folders I guess
Comment 1•19 years ago
|
||
are you blocking remote images? if so, this is a dup of Bug 300749
Feel free to reopen if this is not your problem. *** This bug has been marked as a duplicate of 300749 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Version: unspecified → 1.7 Branch
David, exactly what do you mean by "blocking remote images"? Where in prefs can I see this?
I recognize thay many my symptoms are similar to bug 300749 however, I only have problems with a few special folders. It should be noted though, that all the folders I have a problem with where created using 1.7.10, all working folders where created using 1.7.3 or earlier versions (i've not upgraded in a while). I will wait for bug 300749 to be fixed (which I suspect will be very soon, given how serious it is) and then I will see if my problem persists. If it does I will reopen this one as a unique bug. Meanwhile please tell me where I can see that "blocking remote images" prefs setting?
Comment 5•19 years ago
|
||
edit | preferences | privacy & security | Images - do not load remote images in mail & newsgroup messages. If that doesn't fix the problem, then you have a different problem, I believe. You might check the file permissions on those local folders - there were some regressions having to do with file permissions but I thought those were all fixed before 1.7.10 was released.
That DID solve my problem! Thanks David! So, you do know if this problem fixed in CVS yet?
Comment 7•19 years ago
|
||
it's not, but there is a patch in bug 300749 - just waiting for approval to check it in.
You need to log in
before you can comment on or make changes to this bug.
Description
•