After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 655698 - [abrt] evolution-data-server-3.0.2-1.fc15: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
[abrt] evolution-data-server-3.0.2-1.fc15: Process /usr/libexec/e-addressbook...
Status: RESOLVED OBSOLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
3.0.x
Other Linux
: Normal critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2011-08-01 06:51 UTC by Milan Crha
Modified: 2012-09-04 19:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2011-08-01 06:51:26 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=726356

abrt version: 2.0.3
architecture:   i686
backtrace_rating: 4
cmdline:        /usr/libexec/e-addressbook-factory
comment:        Im not sure, i have found it later...
component:      evolution-data-server
executable:     /usr/libexec/e-addressbook-factory
kernel:         2.6.38.8-35.fc15.i686.PAE
os_release:     Fedora release 15 (Lovelock)
package:        evolution-data-server-3.0.2-1.fc15
reason:         Process /usr/libexec/e-addressbook-factory was killed by signal
6 (SIGABRT)
time:           Mon Jul 25 13:59:20 2011


Comment 1 Milan Crha 2012-09-04 19:12:18 UTC
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.