Red Hat Bugzilla – Bug 214307
Crasher at startup
Last modified: 2013-03-05 22:47:32 EST
Description of problem: Evo crashes at startup. Will attach output. Version-Release number of selected component (if applicable): evolution-2.9.1-2.fc7
Created attachment 140525 [details] output from running evolution
Created attachment 140526 [details] typescript when running gdb also installed evolution-debuginfo packages
Thanks David. From the backtrace I recognize this as one of my own patches, yet I've not seen the crash myself. Does this happen every time or occasionally?
It happened all day yesterday so I had to use Thunderbird (yuck!). Then this morning I started Evolution as part of my daily routine... and now it works. Weird...
It started happening again. Then I updated to Updating: evolution i386 2.9.2-2.fc7 development 13 M evolution-data-server i386 1.9.2-3.fc7 development 3.4 M Updating for dependencies: evolution-data-server-devel i386 1.9.2-3.fc7 development 489 k and it still happens. Back to TB (yuck!).
This also happens on my workstation now evolution-2.9.1-2.fc7 evolution-data-server-1.9.1-2.fc7 gtkhtml3-3.13.1-4.fc7 gtkhtml2-2.11.0-3 My workstation is in the Westford RH office. Let me know if you need access.
This started happening consistently for me after I upgraded my Rawhide machine past FC6. I never once saw the crash when running FC6 + Evo 2.9. Rawhide is pretty borked in general at the moment, so I'm not sure what to make of this.
Created attachment 149206 [details] backtrace This is the backtrace I get. Interestingly it only happens on my user account, a fresh evolution just works. I need my email! ;-) Yell if you need anything.
David, I think this may be the same issue as reported in bug #220714, which was fixed in evolution-2.9.91-3.fc7 (released Feb 15). Have you seen this crasher again recently or are you still on Thunderbird? Richard's backtrace looks like a different bug. I'll try to find a bug report with a similar backtrace, or else open a new one.
Actually, sorry, I "fixed" this by deleting the offending mail ages ago and have been using Evolution error since. So I guess we can close as WORKSFORME?
Okay. The backtraces look very similar to those in bug #220714, so I'll close this as a dupe instead. *** This bug has been marked as a duplicate of 220714 ***