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 706993 - Restart background processes after restore
Restart background processes after restore
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Plugins
3.8.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-plugin-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-08-28 15:04 UTC by Vadim Rutkovsky
Modified: 2014-12-05 11:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vadim Rutkovsky 2013-08-28 15:04:08 UTC 
After restoring evo from backup ~/.cache/evolution directory is still present. The 'worker' processes are still running and display outdated data. The processes should be killed and restarted

STR:
1) Cleanup evo settings and complete first-time wizard
2) Backup evo settings
3) Create a contact/event/email
4) Close evo and restore from backup
5) Start evo
Result: created contact/event/email is still displayed, but cannot be accessed - 'disk I/O' error is displayed
Expected: evo processes are restarted, cache is cleaned

Reproduced on evolution-3.8.5-2.x86_64

Note, that I could not reproduce it in evolution-3.9.90-2.fc21.x86_64
Comment 1 Matthew Barnes 2013-08-28 15:41:08 UTC 
I think the root problem here is we're trying to manage E-D-S backends from an E-D-S client program (Evolution) rather than from E-D-S itself.

I had some thoughts on this awhile back:
https://mail.gnome.org/archives/evolution-hackers/2012-December/msg00025.html
Comment 2 Milan Crha 2014-12-05 11:43:24 UTC 
Created commit 0b4bfe0 in evo master (3.13.9+) [1]
Created commit 8a25e32 in evo evolution-3-12 (3.12.9+)

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