Bug 611863 - [abrt] crash in evolution-2.30.2-1.fc13: soup_message_queue_item_unref: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.2-1.fc13: soup_message_queue_item_unref: Proce...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0d86b4878102cfa5745e679309b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-06 18:10 UTC by Nathan Crubel
Modified: 2011-06-13 18:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-13 18:18:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (54.17 KB, text/plain)
2010-07-06 18:10 UTC, Nathan Crubel
no flags Details

Description Nathan Crubel 2010-07-06 18:10:34 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
comment: Evolution crashed when hitting button Send/Receive.
component: evolution
crash_function: soup_message_queue_item_unref
executable: /usr/bin/evolution
global_uuid: 0d86b4878102cfa5745e679309b6d144d022f9b6
kernel: 2.6.33.5-124.fc13.i686
package: evolution-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Had Evolution Running for a while
2. Hist Send/Receive
3. Evolution crashed

Comment 1 Nathan Crubel 2010-07-06 18:10:36 UTC
Created attachment 429846 [details]
File: backtrace

Comment 2 Nathan Crubel 2010-07-07 13:51:22 UTC
Package: evolution-2.30.2-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Start Evolution
2. Dies before getting all exchange email.
3. 


Comment
-----
Crashed getting email.

Comment 3 Bug Zapper 2011-06-01 14:36:06 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 4 Nathan Crubel 2011-06-13 18:18:28 UTC
No longer running Fedora 13.  Seemed to have been a problem with evolution and exchange server I was connecting too.  I have no information as it started working fine.


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