Created attachment 653104 [details] backtrace evolution Description of problem: After installing clear beta and launching evolution, evolution is stuck and don't closed
Created attachment 653105 [details] evolution-addressbook-factory backtrace
Created attachment 653108 [details] evolution-calendar-factory backtrace
Created attachment 653109 [details] evolution-source-registry backtrace
I see the calendar factory is idle. The addressbook factory is waiting for a response from the source registry, same as evolution is waiting for that response, but the source registry process is also idle. There were similar issues reported already [1], but they were supposed to be fixed. Could you tell me exact versions of evolution-data-server and evolution, please? $ rpm -q evolution-data-server evolution [1] https://bugzilla.gnome.org/show_bug.cgi?id=680961
*** Bug 880878 has been marked as a duplicate of this bug. ***
I just tried to reproduce this with a Live CD Fedora 18 Beta, with evolution-3.6.2-2 and evolution-data-server-3.6.2-1, installed on an empty disk, and after adding an Exchange account to Online Accounts, I run evolution (I waited couple seconds, somehow) and the account was there, with its folder content. Is this the machine where you share your /home with previously installed Fedora 17, with already configured EWS account?
(In reply to comment #6) > Is this the machine where you share your /home with previously installed > Fedora 17, with already configured EWS account? yes
(In reply to comment #4) > Could you tell me exact versions of evolution-data-server and evolution, > please? > $ rpm -q evolution-data-server evolution $ rpm -q evolution-data-server evolution evolution-data-server-3.6.2-2.fc18.i686 evolution-3.6.2-3.fc18.i686
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.