Bug 700693 - [abrt] evolution-data-server-2.32.3-1.fc14: soup_message_io_finished: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.3-1.fc14: soup_message_io_finished: Process...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3c6e2463d1f23f6ca28da509b0f...
: 714337 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-29 03:15 UTC by gb
Modified: 2012-08-16 14:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:18:00 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (28.26 KB, text/plain)
2011-04-29 03:15 UTC, gb
no flags Details

Description gb 2011-04-29 03:15:00 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 28938 bytes
cmdline: /usr/libexec/e-calendar-factory
comment: Evolution is having problems sending mail, its appears it keep doing a DNS lookup but not connecting the gmail server.
component: evolution-data-server
Attached file: coredump, 39448576 bytes
crash_function: soup_message_io_finished
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.12-90.fc14.x86_64
package: evolution-data-server-2.32.3-1.fc14
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303946134
uid: 500

How to reproduce
-----
1.problems connecting and sending mail with google account smtp.gmail.com
2.
3.

Comment 1 gb 2011-04-29 03:15:04 UTC
Created attachment 495701 [details]
File: backtrace

Comment 2 Milan Crha 2011-04-29 07:13:46 UTC
Thanks for a bug report. There is a similar one, bug #675754, but this one is different in one way. What I see in a backtrace is that the CalDAV calendar backend is parsing fetched data from the server, while, in the same time, a proxy settings changed, which results in SoupSession abortion which later crashes in soup_message_io_finished.

It seems to me like an issue with the libsoup, because the calendar does not do anything special with the SoupMessage itself. It's also possible that this is already fixed in Fedora 15, I do not know, I'm rather asking Dan for his opinion on this.

Comment 3 Milan Crha 2011-06-20 06:05:11 UTC
*** Bug 714337 has been marked as a duplicate of this bug. ***

Comment 4 Reinout van Schouwen 2012-03-13 09:51:44 UTC
Observed this problem on F16 still.

Comment 5 Fedora End Of Life 2012-08-16 14:18:03 UTC
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


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