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 785127 - Change in composer body doesn't trigger autosave timeout
Change in composer body doesn't trigger autosave timeout
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Composer
3.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2017-07-19 14:09 UTC by Benjamin Berg
Modified: 2017-07-20 08:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Benjamin Berg 2017-07-19 14:09:13 UTC 
Lately I have had it quite often that I had a draft open for hours even and eventually the shell/evolution/whatever froze and I had to reboot the machine. Afterwards an ancient version of the e-mail would be recovered with only a few lines in it.

This is weird. I would expect the full e-mail to be recovered if I had been away from the composer for only a pretty short time.

This is on Fedora 25 with Evolution 3.22.6.
Comment 1 Milan Crha 2017-07-20 08:59:12 UTC 
Thanks for a bug report. After a little test I figured out what the problem is. When writing to the message body the auto-save code had not been notified about the changes and thus it didn't trigger its one-minute timer to create the backup. Writing elsewhere, like to the message Subject field, works as expected.
I fixed it with the below change. The gnome-3-24 change is slightly different, it doesn't modify size of the public EContentEditorInterface structure.

Created commit 610bb91 in evo master (3.25.90+)
Created commit 9ad42a8 in evo gnome-3-24 (3.24.5+)