272508 - a directory was mysteriously renamed to "d24507d" without me telling it to get renamed

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Peter]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122

I had a directory named "wtf?". the tree was like this:

Local Folders
 \-Outlook Express Mail
   \-Stuff
     \-wtf?

I closed my mail client, then immediately tried to open it again. It didn't
open... I clicked the shortcut again to open it. It opened and I noticed that
the "wtf?" directory was gone. Looking closer, i found a new directory called
"d24507d", which has the same contents as "wtf?" did.

i'm not sure whether or not the directory actually had a question mark in it.

i renamed it back to "wtf?" and tried to reproduce and couldn't.

Reproducible: Couldn't Reproduce
Steps to Reproduce:




I just recently (a few hours ago) upgraded my mozilla version. 
I have mozilla's quick launch enabled. 
My hard drive is fragmented and slow so mozilla sometimes takes a while to load
if the computer has been on for a while. 
(windows sucks with managing virtual memory)

Comment 1

[WADA:World Anti-bad-Duping Agency]

Problem when "?" is included in folder name is DUP of bug 41944.
But "?" problem seems to be fixed by Bug 219586 and Bug 264467, which are for
"/" problem, as I wrote in bug 41944 Comment #67.
What is your build ID of your Mozilla(both before & after your upgrade)?
Does problem still exist even after patch for Bug 219586 and Bug 264467?

By the way, mysterious "d24507d" is "converted" folder name when illegal
character for file name is included in folder name.
In this cases, Mozilla/Thunderbird uses the converted name for folder file name,
then save exact folder name in ".msf" file.
This is current design.
This may be also applicable on some other special characters, which has special
meaning in internal process of Mozilla/Thunderbird.
(But still has some problems. See dependency tree for bug 124287)
Since "folder name" is saved in ".msf" file, deletion of ".msf" file, which is
traditional manual recovery of folder, will force folder name of "d24507d",
which is recovered from file of "d24507d" during restart.
This is also aplicable if ".msf" is comletely corrupted or ".msf" is not created
successufully.
Your case, also bug 41944 case, is probably the case.

Comment 2

[Peter]

I don't know the build ID of my previous Mozilla version. I still have the
installer, but I don't know how to tell you the build ID without installing it
again.


PREVIOUS Mozilla installer:
mozilla-win32-1.8a4-installer.exe  12,301 kB

here's an md5sum if it helps: c292f3d380e786554303087eb61c5bcd

Current mozilla (downloaded yesterday):
mozilla-win32-1.8a5-installer.exe  12,264 kB

46654d56b0cae6945b92b59938b25235

Comment 3

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #2)
> PREVIOUS Mozilla installer            : mozilla-win32-1.8a4-installer.exe
> Current mozilla (downloaded yesterday): mozilla-win32-1.8a5-installer.exe  
> I don't know the build ID of my previous Mozilla version.

Don't worry about for exact build ID.

Chronological is as follows ;
 17-Aug-2004 18:16     /releases/mozilla1.8a3/mozilla-win32-1.8a3-installer.exe
         
 2004-08-18  14:54 PDT Bug 219586 RESOLVED FIXED                                
 29-Sep-2004 02:39     /releases/mozilla1.8a4/mozilla-win32-1.8a4-installer.exe
 2004-10-25  21:45 PDT Bug 264467 RESOLVED FIXED                               
      
 2004-11-01  15:56 PDT Bug 264071 RESOLVED FIXED
 23-Nov-2004 03:37     /releases/mozilla1.8a5/mozilla-win32-1.8a5-installer.exe

Where did you downloaded?
/releases directry? Or /nightly/latest-trunk directry?

If your former 1.8a4 was from /nightly/latest, Bug 219586 was not fixed yet.
("1.8a4" in build ID means after 1.8a3 released but before 1.8a4 release.) 
But if your former 1.8a4 was from /releases, Bug 219586 should have been
applied, then "?" problem would not occur, if my bug 41944 Comment #67 is right.

Does problem stil occur on your newly downloaded 1.8a5?
From which directry did you download your 1.8a5?

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.