Red Hat Bugzilla – Bug 675796
[abrt] evolution-data-server-2.32.1-2.fc14: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Last modified: 2012-08-16 10:15:40 EDT
abrt version: 1.1.14
Attached file: backtrace
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce
1. Right-click address in received e-mail
2. Select Add to address book
3. Select Contacts (Exchange contact list accessed via exchange-connector)
Created attachment 477483 [details]
Thanks for a bug report. What is your libsoup version, please? And if it is not 2.32.2 or later, could you try with it, please?
Dan, does this seem familiar to you, please?
(In reply to comment #2)
> Dan, does this seem familiar to you, please?
(In reply to comment #4)
Good, that's the latest. By any luck, are you able to reproduce this reliably, please? Because you have the latest libsoup then I suspect evolution/evolution-exchange doing bad things with memory, which may valgrind help on that.
In case you can reproduce this, could you try these steps, please?
a) close evolution and e-addressbook-factory
b) make sure you've installed debug info packages for libsoup,
evolution-data-server, evolution and evolution-exchange.
c) run factory on one console as this:
$ G_SLICE=always-malloc valgrind --num-callers=50 \
d) run evolution from another console and reproduce the issue
After it crashes the evo.txt file may contain desired information. Thanks in advance.
I am running FC16 and an facing the same error. However, I am not using Exchanege. My address book is an LDAP server based on Zimbra.
These are the RPM's I have installed. I am happy to do any diagnostics
[chandana@fatta ~]$ rpm -qa | grep -E "evolution|soup"
Created attachment 548947 [details]
Attachment for https://bugzilla.redhat.com/show_bug.cgi?id=675796#c6
Created attachment 548948 [details]
another attchment for https://bugzilla.redhat.com/show_bug.cgi?id=675796#c6
Syslog extract for above
Dec 21 09:31:18 localhost kernel: [ 1973.624053] e-addressbook-f: segfault at 8 ip 000000341722775c sp 00007fed1f52d088 error 6 in libdbus-1.so.3.5.6[341720
Dec 21 09:31:18 localhost abrt: Saved core dump of pid 3885 (/usr/libexec/e-addressbook-factory) to /var/spool/abrt/ccpp-2011-12-21-09:31:18-3885 (54878208
Dec 21 09:31:18 localhost abrtd: Directory 'ccpp-2011-12-21-09:31:18-3885' creation detected
Dec 21 09:31:18 localhost abrtd: New problem directory /var/spool/abrt/ccpp-2011-12-21-09:31:18-3885, processing
My ABRT Tool has created a new bug https://bugzilla.redhat.com/show_bug.cgi?id=769523
(In reply to comment #6)
> I am running FC16 and an facing the same error. However, I am not using
> Exchanege. My address book is an LDAP server based on Zimbra.
Why do you think it's same? It seems to me different, unless some kind of memory corruption. I would rather move to bug #769523 and investigate there, and if it'll turn out that it's the same issue, then we can merge them (though it'll be hard to "prove" with memory corruption issues).
Thanks for looking at this. I have done the update, but could not make it crash. I am not sure if this is connected, but I have not been able to get it to copy my ldap address book for offline operation.
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Updating : evolution-data-server-debuginfo-3.2.2-1.fc16.x86_64 1/4
Updating : evolution-debuginfo-3.2.2-1.fc16.x86_64 2/4
Cleanup : evolution-data-server-debuginfo-3.2.1-1.fc16.x86_64 3/4
Cleanup : evolution-debuginfo-3.2.1-1.fc16.x86_64 4/4
evolution-data-server-debuginfo.x86_64 0:3.2.2-1.fc16 evolution-debuginfo.x86_64 0:3.2.2-1.fc16
(In reply to comment #11)
> Thanks for looking at this. I have done the update, but could not make it
> crash. I am not sure if this is connected, but I have not been able to get it
> to copy my ldap address book for offline operation.
Hmm, hard to tell. You can try to repeat this from scratch, thus it'll re-fetch the crashing contact again. The only thing to do is:
a) stop evolution and all evolution-related processes, like
evolution-alarm-notify, e-calendar-factory, e-addressbook-factory
b) purge the local ldap cache, which is stored in
you can safely delete the folder, because it's just a local copy of
the contacts from the server.
c) continue with steps from comment #5
Evolution has been behaving perfectly since yesterday. Until then I would be getting the above /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV) error at least 3 or 4 times.
I will keep trying to reproduce it.
Thanks for your patience.
This seems to happen only when the computer starts up from cold. I am using a laptop with a wireless connection, and it is possible that this crash is due to the fact that there is no network access when Evolution Data server starts up. I will connect this to a physical connection and report back.
In the mean time, I do not know how this service is started up. I cannot find it under systemd. If the startup can be delayed until a network connection is available, it may resolve the issue.
Thank you, and have a happy Christmas!
(In reply to comment #14)
> In the mean time, I do not know how this service is started up. I cannot find
> it under systemd. If the startup can be delayed until a network connection is
> available, it may resolve the issue.
It's DBus service, and any application using addressbook library from evolution-data-server can start (it's started on demand). It's similar like with e-calendar-factory, which is run on start by evolution-alarm-notify process. If you've set Birthday & Anniversaries calendar to notify you about events from that calendar, then also e-addressbook-factory is opened on session start. Disabling Evolution Alarm Notify process from session start applications may stop running them on start, if it was the cause.
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: