Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 23646 bytes cmdline: /usr/libexec/e-addressbook-factory component: evolution-data-server Attached file: coredump, 27676672 bytes crash_function: g_hash_table_lookup_node executable: /usr/libexec/e-addressbook-factory kernel: 2.6.35.13-91.fc14.x86_64 package: evolution-data-server-2.32.2-1.fc14 rating: 4 reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1307541217 uid: 500 How to reproduce ----- 1. open a photo in gthumb from nautilus while nautilus is still reading 2. in gthumb, press escape to get list of photos 3. watch the crash
Created attachment 503704 [details] File: backtrace
Thanks for a bug report. It seems like a coincidence with the gthumb, as it may not do anything with e-addressbook-factory, which comes from evolution-data-server. Does it help to uninstall evolution-couchdb, if you are not using it? The backtrace suggests that there is a problem with couchdb service, it cannot be contacted by the backend running in a factory process.
I am afraid I sent the wrong info/stack trace with this info. The abrt report tool was a bit confusing to me, sorry. What I described was related to id=705853 which still happens, even after uninstalling evolution-couchdb.
(In reply to comment #3) > I am afraid I sent the wrong info/stack trace with this info. The abrt report > tool was a bit confusing to me, sorry. > > What I described was related to id=705853 which still happens, even after > uninstalling evolution-couchdb. The backtrace seems correct, it's from evolution-data-server package, from e-addressbook-factory process. The steps seems quite unrelated, as I wouldn't expect gthumb being anyhow related to addressbook part of evolution-data-server, though this is a crash after receiving a D-Bus message, thus maybe the crash invoked some kind of message which confused the factory. I would expect the backtrace being different from the above after evolution-couchdb uninstallation. Could you update it, please? (or file a new bug report, both works for me).
I don't think either a gthumb crash is related. This is what probably happened: after a crash of gthumb I reported the item at the top of the abrt interface which is not necessarily related to the latest crash and so I ended up reporting a wrong stacktrace as a gthumb crash. Sorry for the confusion. I'll try to get a new e-addressbook-factory crash and send you the related stack trace today.
Package: evolution-data-server-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. login into a gnome session 2. watch the abrt crash alert 3.
Note: this happened after reinstalling evolution-couchdb. I'll remove the package again so that abrt will be silent when I login. The issue with gthumb is reported here: https://bugzilla.redhat.com/show_bug.cgi?id=705853
(In reply to comment #7) > Note: this happened after reinstalling evolution-couchdb. I'll remove the > package again so that abrt will be silent when I login. OK, thanks for the update. I'm moving this to evolution-couchdb due to your findings. Thanks for an investigation here.
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping