Closed Bug 306343 Opened 19 years ago Closed 17 years ago

folder cannot be renamed or deleted

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: peter, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

A folder was created called 'philips semi' as a second-level subfolder of
local-folders. A message filter was created to send 1 appropriate sender's
messages to that folder. At a later date, the folder was renamed to
'subscriptions' through the right-click 'Rename folder..' dialog box. The rename
did not appear to take effect. Now, the folder shows "philips semi" and cannot
be deleted nor renamed again. Now, a new folder cannot be created with the name
'subscriptions'.  It states that one already exists...

Reproducible: Couldn't Reproduce
Sound like a combination of a few bugs based on the bugzilla search.  Hard to
narrow them down though.
Related to bug #263712??
The only way to work around this bug seems to be creating a completely new folder (different name) and copy over all mails from the older folder.  Very tedious.
what version of thunderbird are you using? Have you tried a 1.5rc1 build yet?
RENAME sometimes fails in Thunderbird 1.5.0.4 and sometimes don't but I can't force the error.
Similar occurrence:  In my Local Folders/Personal Folders/Inbox I had a file named "Rabbit Hollowe" with many sub-files.  I inadvertently changed its name to Hurricane Protection.  When I tried to change it back to "Rabbit Hollowe," the app hung up.  I hit cancel and tried again.  It said a file already existed with that name (it once did bnut not then).  It let me rename to "2235 Rabbit Hollowe" and then rename back to "Rabbit Hollowe."  josh@joshbressler.com  
Similar phenomenon to Bug 65303 Comment #46?
(problem when cyclic renaming. sorry but I doesn't open bug for it yet). 

To all problem reporters:

(Q1)How many times did you rename a folder in a single start of Thunderbird?
    Tried to rename back to one of previous folder names after rename? 
(Q2)Your folder name written in this bug is folder name exactly you typed?
    If folder name has special character such as '\', file/directory name
    for the folder becomes hexa-string, because such special character can not
    be used as file name character. This is also true when URI delimiter chars.
    Bug 65303 Comment #46 is phenomenon in this case.
    And If folder name start or end with "." or end with tilde(~),
    rename or folder access after creation/rename may fail.
    (See Bug 229522, Bug 117840, Bug 198966)
    Comment #6 by Josh Bressler apparently involves this case.
    See meta Bug 124287 for folder name related issues.
(Q3)Do you have virtual folder(search folder, saved search)?
    If you have virtual folder named "X/Y", directory of "X" is created.
    (See Bug 286523) So renaming folder to "X" may be unsuccessuful,
    then it can generate other problems.

Anyway, check all of next for all folder names used by your renaming.
     (1) File for folder          : <Folder_Name> (no file extension)
     (2) Msf file for folder      : <Folder_Name>.msf
     (3) Directory for subfolders : <Folder_Name>.sbd
     (4) Directory of folder name : <Folder_Name> (directory,not file. garbage)
    If special character is involved in folder name, check followings also.
     (5) <Hexa_String>, <Hexa_String>.msf and <Hexa_String>.sbd
(Q4)What files/directories are held in directory for an account?
    (Directory of "Local Folders" in your cases)
    When try to recreate problem, execute step by step check, please.
    (check after creation, check after rename, check after rename back...) 
QA Contact: general
No answer from bug opener even to question on version of Tb...
Closing as WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.