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 545992 - can't restore addressbooks from archive
can't restore addressbooks from archive
Status: RESOLVED DUPLICATE of bug 569909
Product: evolution
Classification: Applications
Component: Contacts
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-08-02 14:31 UTC by CoudCoud
Modified: 2009-08-24 12:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description CoudCoud 2008-08-02 14:31:41 UTC
Please describe the problem:
I recently tried to migrate my evolution parameters to another computer.
My former user directory was in /home/user1. I have used the parameters archival option (I'm french so I don't know it's real name).
On the new computer, I tried to import the .tar.gz file with the appropriate option. The user directory is /home/user2.
The import seems to work, but when I click on the addressbook button, a warning is displayed, saying that /home/user1/.evolution/addressbook/local/system can't be found.
The problem seems to be in ~/.gconf/apps/evolution/addressbook/%gconf.xml : the paths (I have many addressbooks) are not updated from /home/user1 to /home/user2 when the parameters are restored (I manually changed them and re-logged my user account : the problem has been worked-around).
There may be other configuration files that are not updated during the import.
Is there a solution ?
Thank you.

Steps to reproduce:
1. Export your evolution parameters (I have many addressbooks, perhaps there is no bug when you only have one).
2. Import them on another user account
3. Try to use the addressbook component.


Actual results:
a warning is displayed

Expected results:
configuration files are updated during the import, so there are no warnings.

Does this happen every time?
yes

Other information:
Comment 1 Akhil Laddha 2009-08-24 12:43:25 UTC

*** This bug has been marked as a duplicate of bug 569909 ***