Description of problem: Version-Release number of selected component (if applicable): How reproducible: UNKNOWN Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 597463 [details] Corefiles
After upgrdaing to evolution 3.4.3-5 it starts crashing
Thanks for a bug report. I guess you mean evolution-mapi-3.4.3-5. I think it's just a coincidence. With respect of core files, it'll be better to provide backtrace, like if you let ABRT report the bug. Core files are unusable, because they are system dependant. If I open it in gdb then I get on my system: Core was generated by `/usr/libexec/colord'. Program terminated with signal 6, Aborted. #0 0x0000003501235965 in ?? () (gdb) bt #0 0x0000003501235965 in ?? () #1 0x0000003501237118 in ?? () #2 0x0000000000000020 in ?? () #3 0x0000000000000000 in ?? () (gdb) t a a bt Thread 3 (LWP 2536): #0 0x00000035012e8eef in ?? () #1 0x00007f6ad0009e60 in ?? () #2 0x00000000ffffffff in ?? () #3 0x0000000000000003 in ?? () #4 0x00007f6ac80010c0 in ?? () #5 0x0000000000000001 in ?? () #6 0x0000003503247984 in ?? () #7 0x00007f6ad0009e60 in ?? () #8 0xffffffff7fffffff in ?? () #9 0x0000000000000000 in ?? () Thread 2 (LWP 2535): #0 0x0000003501a0b902 in ?? () #1 0x0000000000000000 in ?? () Thread 1 (LWP 2534): #0 0x0000003501235965 in ?? () #1 0x0000003501237118 in ?? () #2 0x0000000000000020 in ?? () #3 0x0000000000000000 in ?? () I'm closing this now, but feel free to provide backtraces. Also, I would file this under colord, the update of evolution-mapi is most likely just a coincidence.