GNOME Bugzilla – Bug 558777
Multiple local addressbooks are considered to be the same addressbook
Last modified: 2016-06-14 09:47:13 UTC
Having more than two local addressbooks does not work properly. Evolution considers the second and the third addressbook to be the same even though they're shown as two separate addressbooks. When contacts are added to or deleted from the third addressbook they will also be added to or deleted from the second addressbook. Steps to reproduce: 1. Delete all addressbooks from Evolution 2. Create new addressbook On This Computer, call it Work 3. Create new addressbook On This Computer, call it Rarely Used 4. Add contact to the Work addressbook 5. View the Rarely Used addressbook Expected results: there should be a contact in the Work addresbook and Rarely Used should be empty Actual results: The contact is shown both in Work and Rarely Used and Evolution thinks they're essentially the same addressbook Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0
It seems that this only happens when I use my ~/.evolution folder and my ~/.gconf/apps/evolution settings. They date back from year 2000 or so, so probably there has been a change at some point that has not been fully backwards compatible. With a clean installation I couldn't reproduce this.
It seems that when this happens the /apps/evolution/addressbook/sources GConf key does not have relative_uri:s in the addressbooks. Here's mine: <?xml version="1.0"?> <group uid="1088366169.10609.3@pc.vesuri.net" name="On This Computer" base_uri="file:///home/vesuri/.evolution/addressbook/local" readonly="no"><source uid="1225535285.5290.0@vesuri.sewerleak.com" name="Personal" relative_uri="system"><properties><property name="completion" value="true"/></properties></source><source uid="1225536560.7651.0@vesuri.sewerleak.com" name="Work" relative_uri=""/><source uid="1225536566.7651.1@vesuri.sewerleak.com" name="Rarely Used" relative_uri=""/></group>
Backing up all evolution data and restoring it did not help. Addressbooks created after that did not have relative_uris either. I was able to work around this as follows: 1. Export all contacts to a vcf file 2. Backup ~/.evolution and ~/.gconf/apps/evolution 3. Delete ~/.evolution and ~/.gconf/apps/evolution 4. Run Evolution again in the clean environment 5. Create the required addressbooks 6. Backup ~/.evolution/addressbook and ~/.gconf/apps/evolution/addressbook 7. Delete ~/.evolution and ~/.gconf/apps/evolution again 8. Restore the first backup 9. Delete ~/.evolution/addressbook and ~/.gconf/apps/evolution/addressbook 10. Restore the second backup 11. Import contacts from the vcf file However, addresbooks created after this are again missing the relative_uris and will be buggy.
> 1. Delete all addressbooks from Evolution You can't do that, you always have the system addressbook non-deletable. > It seems that this only happens when I use my ~/.evolution folder and my ~/.gconf/apps/evolution settings. They date back from year 2000 Haha, OK... Which Evolution version was that?
(In reply to comment #4) > > 1. Delete all addressbooks from Evolution > You can't do that, you always have the system addressbook non-deletable. My bad. Should have typed "Delete all addressbooks except the system addressbook from Evolution" or "Delete all addressbooks that are deleteable". It does not really matter - what matters is that when I create new addressbooks on my setup they don't get relative_uris and thus do not work properly. > > It seems that this only happens when I use my ~/.evolution folder and my > ~/.gconf/apps/evolution settings. They date back from year 2000 > Haha, OK... Which Evolution version was that? I've been using Evolution from the first Ximian versions. Maybe 2000 is incorrect, but at least I've got timestamps from 2001 in some of the files. Again, that's not really relevant. I haven't really had other problems with Evolution with these data files. Something is causing the relative_uris and related directories not to get created but I don't know what it is.
I appear to be running into this bug on Evolution 2.32 (Fedora 14), so it still seems to be around.
*** This bug has been marked as a duplicate of bug 644107 ***