GNOME Bugzilla – Bug 601905
e-addressbook-factory crashed on startup
Last modified: 2011-11-24 06:56:47 UTC
abrt detected a crash. Attached file: backtrace cmdline: /usr/libexec/e-addressbook-factory component: evolution-data-server executable: /usr/libexec/e-addressbook-factory kernel: 2.6.31.5-127.fc12.x86_64 package: evolution-data-server-2.29.2-1.fc12 rating: 2 reason: Process was terminated by signal 11 Core was generated by `/usr/libexec/e-addressbook-factory'. Program terminated with signal 11, Segmentation fault.
+ Trace 219079
Thread 1 (Thread 4993)
on 2.29.3 Using Fedora12 Core was generated by `/usr/libexec/e-addressbook-factory'. Program terminated with signal 11, Segmentation fault.
+ Trace 219159
Thread 1 (Thread 1212)
*** Bug 602058 has been marked as a duplicate of this bug. ***
Can someone who can replicate this run e-addressbook-factory underneath valgrind please, with G_SLICE=always-malloc set. It looks a lot like heap/slice corruption to me.
Created attachment 148056 [details] valgrind trace $ G_SLICE=always-malloc valgrind --tool=memcheck --leak-check=full --trace-children=yes --time-stamp=yes --log-file=/tmp/o --num-callers=20 /usr/libexec/e-addressbook-factory libedata-book-ERROR **: Got result code 2 from requesting name aborting... Aborted (core dumped)
If you see "got result code 2" then eds is about to abort cleanly becuase there is already an instance running. Before running valgrind, please killall e-addressbook-factory.
There is a downstream bug report [1] about the same https://bugzilla.redhat.com/show_bug.cgi?id=540066
have not seen this crash for quite some time.
Can you please check again whether this issue still happens in Evolution 3.0.3 or 3.2.0 and update this report by adding a comment and changing the "Version" field? Thanks a lot.
Please feel free to reopen this bug if the problem still occurs with a newer version of Evolution.