Bug 689358 - [abrt] evolution-2.32.2-1.fc14: soup_session_requeue_message: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: soup_session_requeue_message: Process /usr/bi...
Keywords:
Status: CLOSED DUPLICATE of bug 693186
Alias: None
Product: Fedora
Classification: Fedora
Component: libsoup
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4a18cf51a941dd6c3e56cc6123e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-21 07:59 UTC by Kazimieras Vaina
Modified: 2011-04-08 07:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-08 07:55:39 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (31.29 KB, text/plain)
2011-03-21 07:59 UTC, Kazimieras Vaina 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kazimieras Vaina 2011-03-21 07:59:51 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 32039 bytes
cmdline: evolution
comment: I didn't interact with Evolution, I guess it went down while checking for the new email in the background.
component: evolution
Attached file: coredump, 191078400 bytes
crash_function: soup_session_requeue_message
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.i686.PAE
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: After system lock up I rebooted the computer and started Evolution mail client.
time: 1300692983
uid: 16777216
Comment 1 Kazimieras Vaina 2011-03-21 07:59:54 UTC 
Created attachment 486561 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-22 06:22:28 UTC 
Thanks for a bug report. I'm moving this to libsoup, because the crash happened in its code, and the crashing thread has only main.c from evolution itself.
Comment 3 Lucian Langa 2011-04-08 07:55:39 UTC 
Reassigning based on stacktrace.

*** This bug has been marked as a duplicate of bug 693186 ***
Note You need to log in before you can comment on or make changes to this bug.