Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 58794 bytes cmdline: /usr/libexec/e-addressbook-factory component: evolution-data-server Attached file: coredump, 72609792 bytes crash_function: g_type_instance_get_private 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: 1307449141 uid: 509 How to reproduce ----- 1. just reading mail 2. 3.
Created attachment 503469 [details] File: backtrace
Thanks for a bug report. What is your version of libsoup, please? I found few fixed bugs in libsoup mentioning "process_queue_item", maybe some of them are related, though the latest one mentions libsoup 2.34.0 as a version where it's fixed [1]. Not that I'm sure this is the same issue, though. You can get the version of the installed libsoup by running on console: $ rpm -q libsoup [1] https://bugzilla.gnome.org/show_bug.cgi?id=637741
libsoup-2.32.2-1.fc14.x86_64 yum update libsoup says I'm up to date. Should I jump to fc15? evolution-data-server-2.32.2-1.fc14.x86_64 evolution-help-2.32.2-1.fc14.noarch evolution-data-server-doc-2.32.2-1.fc14.noarch evolution-exchange-2.32.2-1.fc14.x86_64 evolution-data-server-devel-2.32.2-1.fc14.x86_64 evolution-2.32.2-1.fc14.x86_64
(In reply to comment #3) > libsoup-2.32.2-1.fc14.x86_64 > > yum update libsoup says I'm up to date. Should I jump to fc15? Thanks for the update. I'm not sure, let's ask libsoup maintainer. Dan, do you recall anything similar fixing in libsoup, please?
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