Bug 681477

Summary: [abrt] evolution-2.32.1-1.fc14: _int_malloc: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Shane Kerr <shane>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:0f9944b48b366703152673edfc2d87cc5c5ebf44
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-03 07:07:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Shane Kerr 2011-03-02 10:05:05 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 186863 bytes
cmdline: evolution
comment: I was trying to fix a problem where I cannot change appointments that I just added, because it tells me I am not the owner. So I tried to add the calendar back in, using the 'search for calendars on this server' functionality. That did not give me a calendar I could change appointments on, so I found the direct URL for my calendar on our company wiki and tried adding that. This is when Evolution crashed.
component: evolution
Attached file: coredump, 244314112 bytes
crash_function: _int_malloc
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.i686
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299058809
uid: 500

How to reproduce
-----
1. Added Caldav calendar (using "search for calendars on this server")
2. Removed that calendar
3. Added Caldav calendar using URL from my company's administrators
Comment 1 Shane Kerr 2011-03-02 10:05:10 UTC 
Created attachment 481831 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-03 07:07:23 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. The fix is part of 2.32.2, which is in updates testing right now.

*** This bug has been marked as a duplicate of bug 656259 ***