Created attachment 693300 [details] backtrace of the hanged evolution process Description of problem: When I click on an email with invitation, Evolution hangs. The same happens when I try to switch to the calendar mode. However GnomeShell's calendar displays all events from my calendars. Version-Release number of selected component (if applicable): evolution-3.4.4-2.fc17.x86_64 evolution-data-server-3.4.4-4.fc17.x86_64 How reproducible: 100% Steps to Reproduce: 1. run Evolution 2. click on an email invitation or switch to calendar mode Actual results: evolution hangs (backtrace attached) Expected results: invitation is rendered and in the other case calendar mode runs as expected Additional info: After killing evolution-calendar-factory process and running evolution by 'evolution -c calendar' evolution runs and in email mode renders invitations, but I cannot see calendars' names.
Thanks for a bug report. Based on the backtrace, the evolution parts is waiting for a response from the evolution-calendar-fatory, which might be stuck for some reason. The next time it happens to you, please get a backtrace of the evolution-calendar-factory. Thanks in advance.
Yeah, I thought so. Next time it happens I'll upload the backtrace from the calendar-factory.
Created attachment 694299 [details] backtrace from evolution-calendar-factory when evolution hanged requested backtrace attached
(In reply to comment #3) > Created attachment 694299 [details] > backtrace from evolution-calendar-factory when evolution hanged > > requested backtrace attached This time it wasn't stucked completely, but it took ages before the invitation finally got rendered. And GnomeShell's calendar still works so this was a different case from what I've seen before because those cases made GnomeShell's calendar stop working. I'll attach the backtrace for the worse case one I hit it again.
(In reply to comment #4) > (In reply to comment #3) > > Created attachment 694299 [details] > > backtrace from evolution-calendar-factory when evolution hanged > > > > requested backtrace attached > This time it wasn't stucked completely, but it took ages before the > invitation finally got rendered. And GnomeShell's calendar still works so > this was a different case from what I've seen before because those cases > made GnomeShell's calendar stop working. I'll attach the backtrace for the > worse case one I hit it again. One more thing from this case. I see lines like: Failed to load the calendar 'google-Public' (Timeout was reached) for all my non-local calendars in the rendered invitation. So I guess this caused the long delay before rendering. However I have no idea why this timeout happened.
okay, so in the "real hang case" where also GnomeShell's calendar stops showing appointments the backtrace from the calendar-factory is the same as attachment 694299 [details]. It looks like some deadlock. And now, a while after the hang I ABRT appeared with a crash detected in Evolution and pointed me at bug #753850
Thanks for the update. From the backtrace, I think this is fixed in libsoup 2.40.3, do you have it installed? Or could you install it, please? Note the install will require restart of the factory, though it's a little bit tricky, thus a whole machine restart would be better.
(In reply to comment #7) > Thanks for the update. From the backtrace, I think this is fixed in libsoup > 2.40.3, do you have it installed? Or could you install it, please? Note the > install will require restart of the factory, though it's a little bit > tricky, thus a whole machine restart would be better. I have: libsoup-2.38.1-3.fc17.x86_64 but a newer version is available only in rawhide and updating libsoup from rawhide would update e.g. all ghc-* and gnome-* packages among a lot of others.
OK, it's part of fedora 18, thus maybe when you get to update to it, then you can retest the issue. I'm setting this to need-info for now. (I do not want to close it to current release without confirmation.)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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.
I didn't see this problem in F18+