GNOME Bugzilla – Bug 329352
EDS Crashes At Start of Evolution.
Last modified: 2013-09-14 16:49:28 UTC
Please describe the problem: I can't get Evolution running to test, EDS always crashes immediately Program received signal SIGABRT, Aborted.
+ Trace 65786
Thread 1097264048 (LWP 13743)
Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Dave: I am not seing this bug in my setup. Can you confirm if its happening in other machine also ?. To reproduce this bug i need package info in your system. type rpm -qa > list, attach that list to this bug
I'm going to close the bug. If the debugging information isn't useful, I don't know what else I can do. We won't be taking the time to load on other computers. All Evolution sessions will be run from this one server...there won't be any client devices for Evo. It either works on the server, or not. I continue to get oddness with EDS. It seems to go in streaks, where it's working poorly 2-3 times and then starts working again.
Am now working on a patch which would fix all the random crashes in EDS while closing evolution. It will be given for testing tommorow.
I don't this its invalid, we are just trying to sort out the case where it could be reproduced. This is a very critical issue. We are trying to set the similar environment where the bug can reporduced. So if you could provide information on the services and channels your using in red-carpet or some information about from where you update other packages, it would be really useful to sort it out.
It would be really useful if you provide us the traces of all the threads.
per IRC conversation with Harish, he wanted me to remind everyone that we are blowing out some files before Evolution starts that might be causing problems. In the script that calls Evolution I do a : find $HOME/.evolution -name cache -exec rm -r "{}" \; This is needed to work around about 3 bugs related to cache that look like they won't make 2.6.
Debugging eds and evolution are nearing the edge of my expertise area. I'm getting a lot of spewage that I don't know what it means. Right before an EDS crash, yet I placed no breakpoints: Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread -1224070224 (LWP 20712)] 0xb75e1871 in __nptl_create_event () from /lib/tls/libpthread.so.0 (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0xb75e2a8d in start_thread () from /lib/tls/libpthread.so.0 (gdb) cont Continuing.
possible crash information:
+ Trace 66906
Thread 3 (Thread -1269093456 (LWP 22634))
And another:
+ Trace 66907
Thread 1 (Thread -1219766592 (LWP 23472))
These are same traces as bug 334065. Am working on it.
*** This bug has been marked as a duplicate of 323275 ***