Bug 726893 - Random failure while trying to move emails from folder to folder: No such file or directory. (ENOENT)
Summary: Random failure while trying to move emails from folder to folder: No such fil...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-30 11:06 UTC by Gilboa Davara
Modified: 2011-08-01 06:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-01 06:22:32 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 654628 0 None None None Never

Description Gilboa Davara 2011-07-30 11:06:36 UTC 
As the title suggest, 4 out 5 attempts to move email from one folder to another (usually from sent items) fails with -ENOENT error.
"Error while moving messages to folder Inbox/XXX/#XXX
Cannot transfer message to destination folder: No such file or directory."
(Please notice the # in the target folder name).

Evolution version: 
evolution-3.0.2-3.fc15.x86_64

.local/share/evolution and .config/evolution are
symbolic links to ~/Documents/evolution (to ease backups).
Evolution database was originally created in Fedora 2, continuously upgrade with each subsequent Fedora release.

Bug also reported upstream, keeping this bug report as reference.

- Gilboa
Comment 1 Milan Crha 2011-08-01 06:22:32 UTC 
Thanks for a bug report. This doesn't sound like a Fedora specific issue, and as such should be dealt with upstream, thus I'm closing this in a favour of your upstream bug. It's always easier to deal with issue in one bugzilla and bug report than updating more places multiple times with the same text.
Note You need to log in before you can comment on or make changes to this bug.