Bug 908344

Summary: [abrt] evolution-3.4.4-2.fc17: lookup_queued_alarm: Process /usr/libexec/evolution/3.4/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Per Sjoholm <Per.t.Sjoholm>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:36f8b4ddae9f0981d831b692326081678d8b6afa
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-07 08:05:33 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:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: build_ids
none
File: open_fds none

Description Per Sjoholm 2013-02-06 13:26:35 UTC 
Description of problem:
Cleared data
rm -rf ./.config/evolution  ./.cache/evolution ./.gconf/apps/evolution ./.local/share/evolution

started evolution and configured imap account to own uw-imap server.
Has a google account configured in system setting

Rebooted and logged in.


Version-Release number of selected component:
evolution-3.4.4-2.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/3.4/evolution-alarm-notify
crash_function: lookup_queued_alarm
kernel:         3.6.11-5.fc17.i686

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 lookup_queued_alarm at alarm-queue.c:331
: #1 open_alarm_dialog at alarm-queue.c:1440
: #2 tray_icon_clicked_cb at alarm-queue.c:1488
: #3 icon_activated at alarm-queue.c:1513
: #4 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115
: #5 _g_closure_invoke_va at gclosure.c:840
: #8 emit_activate_signal at gtkstatusicon.c:1277
: #9 gtk_status_icon_button_press at gtkstatusicon.c:1628
: #10 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
: #15 gtk_widget_event_internal at gtkwidget.c:6380

Potential duplicate bug: 702810
Comment 1 Per Sjoholm 2013-02-06 13:26:38 UTC 
Created attachment 693912 [details]
File: core_backtrace
Comment 2 Per Sjoholm 2013-02-06 13:26:41 UTC 
Created attachment 693913 [details]
File: environ
Comment 3 Per Sjoholm 2013-02-06 13:26:43 UTC 
Created attachment 693914 [details]
File: backtrace
Comment 4 Per Sjoholm 2013-02-06 13:26:45 UTC 
Created attachment 693915 [details]
File: limits
Comment 5 Per Sjoholm 2013-02-06 13:26:47 UTC 
Created attachment 693916 [details]
File: cgroup
Comment 6 Per Sjoholm 2013-02-06 13:26:49 UTC 
Created attachment 693917 [details]
File: smolt_data
Comment 7 Per Sjoholm 2013-02-06 13:26:51 UTC 
Created attachment 693918 [details]
File: executable
Comment 8 Per Sjoholm 2013-02-06 13:26:54 UTC 
Created attachment 693919 [details]
File: maps
Comment 9 Per Sjoholm 2013-02-06 13:26:56 UTC 
Created attachment 693920 [details]
File: dso_list
Comment 10 Per Sjoholm 2013-02-06 13:26:58 UTC 
Created attachment 693921 [details]
File: proc_pid_status
Comment 11 Per Sjoholm 2013-02-06 13:27:00 UTC 
Created attachment 693922 [details]
File: var_log_messages
Comment 12 Per Sjoholm 2013-02-06 13:27:02 UTC 
Created attachment 693923 [details]
File: build_ids
Comment 13 Per Sjoholm 2013-02-06 13:27:04 UTC 
Created attachment 693924 [details]
File: open_fds
Comment 14 Milan Crha 2013-02-07 08:05:33 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. It's from older Fedora, but the associated upstream bug report is still valid, as it can happen from time to time, which proves bug #875525. The crash is in the alarm notifications code, thus it's about reminders in your calendar(s).

*** This bug has been marked as a duplicate of bug 702810 ***
Comment 15 Per Sjoholm 2013-02-07 10:23:35 UTC 
Which bug report is open ?
they are all closed with duplicate of
Comment 16 Per Sjoholm 2013-02-07 10:28:25 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=663875 is on 2.3 and Fedora 14 and is closed upstream

https://bugzilla.redhat.com/show_bug.cgi?id=875525 is on fedora 18 and is closed.

Where is the open bugreport for a current version of fedora ?
Comment 17 Milan Crha 2013-02-08 15:00:25 UTC 
The upstream bug [1] is opened. Basically, the defect is not a Fedora specific, thus its dealt with it in upstream, rather than here.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=325508