[imap] moving a folder results in its deletion

sounds like a serious data loss bug, assigning to the desktop team to take a look

Mathieu, as you are the closest thing to a "resident Evolution master", would you mind having a look at this? If it's reproducible, we should at least forward it upstream, and perhaps disable the drag&drop functionality as a workaround if it isn't easy to fix properly.

Thanks!

Err, sorry about "closest thing"! I just realized that might sound quite rude.

I can't successfully reproduce this.

Michał, would you be able to offer more details, such as at least what kind of account is in use where you can reproduce the issue? Is it a Maildir, mbox, or other kind of account?

Hey, it's a Maildir over "IMAP+" (dovecot).

I'll investigate more and try and report, it might be limited to my current account setup or something.

Will also try and get as much logs as possible from both sides.

Hey, I can reproduce on a "clean" account, didn't yet try in a clean Evolution setup as Guest user, will do so and report back. I'm attaching the camel debug log and an uninteresting dovecot log.

Reproduced in a guest account, got some IMAP logs, too.

If I read file 20120327-151048-20023.in correctly:

> D00046 DELETE "Templates.Test 1"
> D00048 RENAME "Templates.Test 1" "Test 1"

That does sound quite like "rm -Rf /" to me...

Steps to (reliably) reproduce:
* create a folder
* create a subfolder under <folder>
* move <folder> under another folder
* move <folder> back under account
* repeat until Evolution reports "no such folder"

So yes, I can indeed reproduce this (my issues were unrelated, just a sadly configured instance).

I'm unable to make enough sense of it to tackle this myself, but I've file the bug upstream.

I don't know if this is related, but I have just encountered some Evolution folder-moving weirdness in 11.10.

I was trying to rename or move various local folders (maildir) and would get error messages about non-existent folders/files. I would restart Evolution and then things would look (more) OK. Looking at the folder structure in the file system it appeared that the folders were being renamed in the background (these were big folder hierarchies with hundreds of nested folders) and while the filesysten rename was in progress the Evolution folders wouldn't play nice. (There was also no indication in Evolution that a background operation was running.)

Also, when the top-level evolution folder had subfolders but no messages the corresponding filesystem folder didn't exist. If I created a corresponding folder in the filesystem I was then able to rename the folder in Evolution.

Ross, sounds to me like what you are seeing is actually a different issue. Could you please file a bug for that particular case and comment back here with the bug number so that I can get back to it and triage it? Please make sure to use 'ubuntu-bug evolution'.
Thanks!

Is that still an issue in quantal?

see gnome-bugs: RESOLVED OBSOLETE
please change status to Won't fix

change status to invalid