Bug 675754 - [abrt] evolution-data-server-2.32.1-1.fc14: soup_message_io_finished: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.1-1.fc14: soup_message_io_finished: Process...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e484ca12d4d49688565af8cefc4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-07 16:15 UTC by Maksym Sh
Modified: 2011-02-08 10:58 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-08 10:58:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (23.44 KB, text/plain)
2011-02-07 16:15 UTC, Maksym Sh
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 637741 0 None None None Never

Description Maksym Sh 2011-02-07 16:15:37 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
comment: I
component: evolution-data-server
crash_function: soup_message_io_finished
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.10-74.fc14.i686
package: evolution-data-server-2.32.1-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297094976
uid: 500

How to reproduce
-----
1. I simply edited some allert in my gmail.account when I had saw  notification about it.

Comment 2 Milan Crha 2011-02-08 10:58:02 UTC
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=637741


Note You need to log in before you can comment on or make changes to this bug.