Bug 714617 - [abrt] evolution-2.32.2-1.fc14: tooltip_event_cb: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: tooltip_event_cb: Process /usr/bin/evolution ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6423c5d75b38ce470fc0d7689d6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-20 09:16 UTC by Reinhard Bayer
Modified: 2011-06-21 04:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-21 04:55:47 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (38.40 KB, text/plain)
2011-06-20 09:16 UTC, Reinhard Bayer
no flags Details


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

Description Reinhard Bayer 2011-06-20 09:16:04 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 39326 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 82026496 bytes
crash_function: tooltip_event_cb
executable: /usr/bin/evolution
kernel: 2.6.35.13-92.fc14.i686
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: 1308557337
uid: 500

How to reproduce
-----
1. Open Calendar
2. Delete some recurrend calendar entries one after the other 
3. Crash...

Comment 1 Reinhard Bayer 2011-06-20 09:16:09 UTC
Created attachment 505557 [details]
File: backtrace

Comment 2 Milan Crha 2011-06-21 04:55:47 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=653072


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