GNOME Bugzilla – Bug 249448
Should evolution close eds and alarm-notify on exit?
Last modified: 2013-09-13 00:48:24 UTC
When closing evolution the evolution-wombat and evolution-alarm-notify processes are left running unless an explicit "evolution --force-shutdown" is executed. This means that the calendar and contacts files are still in use between evolution sessions. This is not a problem if the same machine is used all the time but if multiple machines are used and especially if the machines have separate filestores which are kept in synchronization it seems that data updates can be lost. For example if I use machine agwisance at work then copy my contact and calendar information to elon at home then make changes to the databases at home then copy them back to work I find that unless I manually ensure evolution-wombat is closed at both sites before making any of the copies in either direction there seems to be loss of updated data in both calendar and contacts. I think it would be good to have an option in evolution setup to say always kill all spawned processes on shutdown so as to cover failing to manually issue the necessary command after closing evolution -- or is this me just being too wimpish?
still valid in 2.3.5.1, reassigning to harish. it's called "evolution-alarm-notify" and "evolution-data-server" nowadays, chanigng subject to reflect this. ...why does ps ax | grep evo tell me that the process is called "evolution-data-server-1.4", by the way? i'm running eds-1.3.5 here! harish?!
perhaps related/the same as bug 253904? does this also depend on bug 219197?
the name is the name of the program, not the version of it .. Anyway, i would say to the title, "no, it shouldn't", the whole point of it is it can notify you without having evolution running. If you are doing out-of-band synchronisation, then you have to shutdown eds anyway; not a 'supported' operation anyway, and not a bug.
One half of this bug is a dup of bug 253904; the other half a dup of bug 225828. Picking one of the two at random. *** This bug has been marked as a duplicate of 225828 ***