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 672474 - Flaw in GOA synchronization logic
Flaw in GOA synchronization logic
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
3.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[goa]
: 660378 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-03-20 14:43 UTC by Matthew Barnes
Modified: 2013-09-13 01:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Sync changes back to GConf (3.29 KB, patch)
2012-03-20 14:47 UTC, Matthew Barnes 		committed Details | Review

Description Matthew Barnes 2012-03-20 14:43:41 UTC 
When a GNOME Online Account is deleted while Evolution is not running, it's possible for Evolution to be left with an "orphaned" account that's no longer linked to GOA.

When Evolution starts up it scans its own accounts for those with "goa-account-id" tags.  It then matches those tags to actual GOA proxy objects via D-Bus.  If it fails to find a match, Evolution is supposed to delete its own account.

The problem is Evolution deletes the account in memory, but forgets to sync the deletion back to GConf where account data is permanently stored.

Filing this as a bug to get release team approval for Evolution 3.4.0.
Comment 1 Matthew Barnes 2012-03-20 14:47:34 UTC 
Created attachment 210181 [details] [review]
Sync changes back to GConf

Immediately synchronize account additions and removals back to GConf throughout the "online-accounts" module.
Comment 2 Matthew Barnes 2012-03-20 15:46:36 UTC 
Fixed for Evolution 3.4.0 with release team approval:
http://git.gnome.org/browse/evolution/commit/?id=83f7de0aed96d64229580f540cd56b56e8656c80
Comment 3 Milan Crha 2012-05-17 11:59:03 UTC 
*** Bug 660378 has been marked as a duplicate of this bug. ***