Bug 84076 - deleting non-empty imap-folder causes segfault
deleting non-empty imap-folder causes segfault
Product: Red Hat Public Beta
Classification: Retired
Component: evolution (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
Blocks: 79579
  Show dependency treegraph
Reported: 2003-02-11 17:03 EST by Tom Vergote
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-12 15:16:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tom Vergote 2003-02-11 17:03:56 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030120

Description of problem:
When deleting a non-empty imap-folder with subfolders i got the error message
"cannot delete folder: cannot create a folder with that name" after which
evolution segfaults.

I am connecting to a courier imap server.
The error only happens when you try to delete a folder with subfolders, there
can be messages in them, no problem, and i could delete them one by one moving
up the tree too, but as soon as i tried to delete a folder with subfolders i had
the error

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start evolution
2. connect to a courier imap server
3. delete a folder which has subfolders

Actual Results:  evolution segfaults

Expected Results:  the folder and subfolders should've been deleted

Additional info:

it might be a long shot, but i think it's got something to do with the dot's in
the folders naming. 
they go:
Comment 1 Jeremy Katz 2003-02-12 15:16:22 EST
The segfault is fixed in 1.2.2.  Deleting folders with subfolders can be racy so
is disallowed intentionally (although, yes, the error message is a little

Note You need to log in before you can comment on or make changes to this bug.