After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613904 - Autosave file sometimes does not disappear along with composer
Autosave file sometimes does not disappear along with composer
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer]
Depends on:
Blocks:
 
 
Reported: 2010-03-25 10:37 UTC by Michel Dänzer
Modified: 2011-03-01 11:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michel Dänzer 2010-03-25 10:37:26 UTC 
After sending a message, sometimes the corresponding ~/.evolution/.evolution-composer.autosave-* file remains. This means the composer will be spuriously restored next time Evolution starts. I haven't been able to determine any pattern for when this happens yet.

This is a regression from 2.28.x.
Comment 1 Matthew Barnes 2010-03-25 13:08:15 UTC 
There have been a number of changes and fixes to the autosave code over the course of 2.29.  Exactly which version are you using, please?
Comment 2 Michel Dänzer 2010-03-25 13:43:31 UTC 
Yeah sorry, should have mentioned this before: It's 2.29.92.1. I don't see any autosave related changes since then on the gnome-2-30 branch.
Comment 3 Michel Dänzer 2010-03-31 13:15:21 UTC 
It can also happen after closing the composer manually, I guess it boils down to the new title.
Comment 4 Michel Dänzer 2010-04-12 15:48:43 UTC 
The patches from bug 220672 seem to fix this. Maybe just coincidence, or maybe this indicates that the problem could be related to an autosave cycle being in progress while the composer goes away.
Comment 5 Michel Dänzer 2011-03-01 11:05:32 UTC 
Seems fixed in 2.32.