Bug 875525

Summary: [abrt] evolution-3.6.1-1.fc18: lookup_queued_alarm: Process /usr/libexec/evolution/3.6/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Amir Hedayaty <hedayaty>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: liblit, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:36f8b4ddae9f0981d831b692326081678d8b6afa
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-04 08:13:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amir Hedayaty 2012-11-11 22:24:45 UTC
Version-Release number of selected component:
evolution-3.6.1-1.fc18

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/3.6/evolution-alarm-notify
crash_function: lookup_queued_alarm
kernel:         3.6.6-3.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 lookup_queued_alarm at alarm-queue.c:328
: #1 open_alarm_dialog at alarm-queue.c:1438
: #2 tray_icon_clicked_cb at alarm-queue.c:1486
: #3 icon_activated at alarm-queue.c:1511
: #4 _g_closure_invoke_va at gclosure.c:840
: #7 emit_activate_signal at gtkstatusicon.c:1278
: #8 gtk_status_icon_button_press at gtkstatusicon.c:1604
: #9 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
: #14 gtk_widget_event_internal at gtkwidget.c:6301
: #15 gtk_widget_event at gtkwidget.c:5958

Potential duplicate bug: 702810

Comment 1 Milan Crha 2013-02-04 08:13:39 UTC
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate. I updated the associated upstream bug report too.

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