GNOME Bugzilla – Bug 542284
Contacts are inaccessible.
Last modified: 2009-09-25 06:24:54 UTC
Please describe the problem: When I tried to access my contacts (address book), I get an error pop-up that tells me I should verify that the path /home/mrichter/.evolution/addressbook/local/system exists and can be accessed. It does, I own it, I have write access to it, but it refuses to open my contacts. I tried copying the files out and using a fresh directory, then copying them back, but to no avail. Now Evo reports no contacts at all, even though I have several in the address book. I should note that /home is an NFS-mounted directory to which I have full rights on both the local and remote systems (with the same userid and groupid). Steps to reproduce: 1. Open Evolution 2. Go to the contacts window 3. Actual results: I was getting the error I described above. Now I just get an empty contacts folder. Expected results: I expect to see my contacts as recorded in the addressbook file. Does this happen every time? So far, yes. Other information: This was working on CentOS (RHEL) 5.1 and stopped working on CentOS 5.2.
Is there any shell output?
I usually run evolution from a launcher or keyboard shortcut, but when I run it from a command line, no, there is nothing. In fact, if I run it under strace and collect the output to a file, there is no attempt to access the addressbook in the file at all. I'm beginning to think that something is corrupting older addressbook files because if I delete the old ones, evo will create new ones that are just fine, except that they are empty. I can't afford to lose my contacts like that. Also, at home I am running on an AMD 64 x2 system with 4GB of memory, at work I have a (lame) P4 with 1GB of memory, so I'm reasonably certain it is not a 32 vs 64 bit or AMD vs Intel problem.
Does this solution help ? http://mail.gnome.org/archives/evolution-list/2009-April/msg00139.html This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.26. Can you please check again whether this issue still happens in Evolution 2.24 or 2.26 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.28.0 or later), please reopen. thanks in advance.