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 739562 - Message composer autosave not updating
Message composer autosave not updating
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-11-03 13:31 UTC by Ian Campbell
Modified: 2014-11-06 14:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ian Campbell 2014-11-03 13:31:00 UTC
It appears that evolution is no longer frequently saving unsent mails in the composer, such that when it is restarted after a crash any unsent mails revert to a version from tens of minutes ago. Mostly they appear to be a version from not long after I opened the composer window (suggesting perhaps that autosave only happens once near the start?).

This seems to happen consistently regardless of whether I was actively editing the message or had just left it sitting on my desktop for a while.

For example right now I have an autosave file:

-rw------- 1 ianc xendev 690 Nov  3 13:10 .local/share/evolution/.evolution-composer.autosave-KS8TOX

It is currently 1325 and the autosave does not contain any of what is currently in the editor window which I've written in the last 15 minutes.

FWIW hitting the Save Draft button in the UI doesn't cause the autosave file to be updated, although a copy is correctly saved in my Drafts folder (I presume these two things are actually completely independent)
Comment 1 Milan Crha 2014-11-06 14:53:05 UTC
Thanks for a bug report. That is my fault, I blindly spread a callback registration for property change notifications which makes sure that the callback is not called on a false positive notification, that is when the old value really didn't change, but the composer-autosave module relies on the false change notifications, which I didn't notice.

Created commit eeaf950 in evo master (3.13.8+) [1]
Created commit fba9dc8 in evo evolution-3-12 (3.12.8+)

[1] https://git.gnome.org/browse/evolution/commit/?id=eeaf950