Hide Forgot
Created attachment 501334 [details] Output of evolution during backup/restore. Description of problem: I am trying to migrate from Fedora 11 to Fedora 15. Under Evolution 2.26.3, I select File->Backup Settings... and save into evolution-backup.tar.gz. I transfer this file to a new computer running Fedora 15 x86_64, start Evolution 3.0.1 (from the command line), and attempt to restore these settings on the new computer. After an alert stating that the new default format for Evolution mail folders is maildir, I proceed. Evolution hangs before completing the restore. I *am* able to restore my evolution-backup.tar.gz to the versions of Evolution present on Fedora 13 and Fedora 14. I have tried a backup/restore from Fedora 13/Evolution 2.30.3 to Fedora 15/Evolution 3.0.1 without success. Version-Release number of selected component (if applicable): Evolution 3.0.1 How reproducible: Always (I've tried several times.) Steps to Reproduce: 1. Attempt backup/restore of mail from prior version of Evolution to Evolutions 3.0.1 from one computer to another computer 2. 3. Actual results: Restore process hangs after trying to convert mboxs to maildirs. Expected results: Successful restore of all Evolution data. Additional info: Attached is the output in the terminal from which I run Evolution 3.0.1.
I have found that by renaming the files /home/test/.local/share/evolution/mail/local/folders.db-journal /home/test/.local/share/evolution/mail/local/folders.db-wal I could obtain access to my local mail, with the caveats that my inbox included a lot of mail I had previously reclassified as spam. I did an strace on Evolution 3.0.1 and it seems to be hanging around here (this sequence is repeated about 10000 times in my strace output, until I kill evolution): access("/home/test/.local/share/evolution/mail/local/folders.db-journal", F_OK) = 0 stat("/home/test/.local/share/evolution/mail/local/folders.db-journal", {st_mode=S_IFREG|0644, st_size=4640, ...}) = 0 fstat(37, {st_mode=S_IFREG|0644, st_size=26617856, ...}) = 0 lseek(37, 24, SEEK_SET) = 24 read(37, "\0\0\0W\0\0e\212\0\0\0\0\0\0\0\0", 16) = 16 fstat(37, {st_mode=S_IFREG|0644, st_size=26617856, ...}) = 0 access("/home/test/.local/share/evolution/mail/local/folders.db-wal", F_OK) = -1 ENOENT (No such file or directory) fstat(37, {st_mode=S_IFREG|0644, st_size=26617856, ...}) = 0 lseek(37, 23985152, SEEK_SET) = 23985152 read(37, "\n\0\0\0\n\1\320\0\2@\2x\2\260\2\350\3 \3X\2\10\3\220\3\310\1\320\0\0\0\0"..., 1024) = 1024
Thanks for a bug report. It seems to me that evolution is trying to restore your folders.db file. Did you move from a 32bit system to a 64bit? Is it possible to get a backtrace of hung evolution, please? You can do that by a command like this: $ gdb --batch --ex "t a a bt" -pid=PID &>bt.txt where PID is a process ID of running evolution (make sure you've installed debug info packages for evolution-data-server, evolution and sqlite3). I think, based on your strace output, that those calls come from sqlite3 itself, maybe it tries to upgrade the folders.db file content to a newer version. The backtrace may show us that.
Created attachment 502147 [details] Backtrace of hung evolution during restore This is the output of evolution after installing various debuginfos and running gdb --batch --ex "t a a bt" -pid=PID &>bt.txt, as requested.
Thanks for the update. This really seams like something with sqlite3, as it's hung in it. I'm moving this bug report there, maybe its maintainer will have any advice on the issue and whether we can do anything from evolution to prevent this hung.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping