GNOME Bugzilla – Bug 589114
Unable to convert mailboxes from Jaunty to Karmic versions
Last modified: 2013-09-13 01:04:31 UTC
+++ This bug was initially created as a clone of Bug #559153 +++ Use Case: 1. In ubuntu 9.04, do a backup of Evolution using File > Backup Settings. This should be done to an external drive. 2. Do a clean install of Ubuntu 9.10 (alpha 2) and apply all updates (as of Jul-19-2009). The version of Evolution is 2.27.4.1. 3. Start Evolution. The initial installation panel appears, indicating that this is the first time the user has run Evolution. 4. Select Forward. There is a screen that should allow you to specify that you wish to restore from backup. 5. Select the checkbox (we do want to restore from a backup) and locate the backup that was made in Step 1. 6. Select the Apply button. There is a delay once the Apply button is selected before anything happens. 7. The Restore screen appears, and suitable progress is indicated. After a period of time, the screen disappears, indicating that the backup is complete. 8. The expected result is that Evolution will open and all folders, mail, contacts, accounts, and calendar entries will appear. The actual result is that the initial panel (described in Step 3) is redisplayed. It appears that the restore process is not working. When the .evolution folder is checked, there are only the standard contents - none of the contents that were in the backup will appear. This is a critical bug, since many users, myself included, to a re-install whenever we upgrade and the restore capability in evolution is absolutely critical for the success of that process. I noticed as well that this bug appeared, and was corrected, in prior versions of Evolution. I'd like to recommend that this simple test should be used as part of a standard set of regression tests prior to releasing a version of Evolution. I reported the bug in ubuntu here: https://bugs.launchpad.net/bugs/401521 and they have requested that I report the bug to you.
There is no sense in cloning a valid, open bug. Please add a comment to bug 559153 instead. *** This bug has been marked as a duplicate of 559153 ***