Bug 723039 - [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by sign...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f094e22d0956793713e0bdcf0e7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-18 20:03 UTC by David R. Fischer
Modified: 2011-07-26 10:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-26 10:03:50 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (92.56 KB, text/plain)
2011-07-18 20:03 UTC, David R. Fischer 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


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

Description David R. Fischer 2011-07-18 20:03:21 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 94779 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 284905472 bytes
crash_function: mail_paned_view_update_view_instance
executable: /usr/bin/evolution
kernel: 2.6.35.13-92.fc14.x86_64
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: Shutting down application
time: 1311019069
uid: 500
Comment 1 David R. Fischer 2011-07-18 20:03:24 UTC 
Created attachment 513677 [details]
File: backtrace
Comment 2 Milan Crha 2011-07-26 10:03:50 UTC 
Thanks for a bug report. I moved this upstream as [1]. 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=655330
Note You need to log in before you can comment on or make changes to this bug.