Bug 689080 - [abrt] evolution-2.32.2-1.fc14: e_day_view_on_text_item_event: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: e_day_view_on_text_item_event: Process /usr/b...
Keywords:
Status: CLOSED DUPLICATE of bug 653534
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:80d1156318f7270a1f7c9ff5236...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-19 05:51 UTC by David Hampton
Modified: 2011-03-21 08:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-21 08:04:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (88.37 KB, text/plain)
2011-03-19 05:51 UTC, David Hampton 		no flags Details
View All

Description David Hampton 2011-03-19 05:51:25 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 90487 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 71127040 bytes
crash_function: e_day_view_on_text_item_event
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.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)
time: 1300513599
uid: 1001

How to reproduce
-----
1. Syncronize PDA and have the bloody program decide to duplicate all the data from the PDA instead of synchronizing it.
2. Spend an hour selecting the duplicates, one by one, and deleting them.
3. Watch evolution crash at random points.
Comment 1 David Hampton 2011-03-19 05:51:28 UTC 
Created attachment 486362 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-21 08:04:42 UTC 
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate.

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