Created attachment 739668 [details]
File: maps

Created attachment 739669 [details]
File: var_log_messages

Created attachment 739670 [details]
File: open_fds

Created attachment 739671 [details]
File: environ

Created attachment 739672 [details]
File: dso_list

Created attachment 739673 [details]
File: limits

Created attachment 739674 [details]
File: sosreport.tar.xz

Created attachment 739675 [details]
File: backtrace

Created attachment 739676 [details]
File: build_ids

Created attachment 739677 [details]
File: cgroup

Opened upstream bug report for the same:
https://bugzilla.gnome.org/show_bug.cgi?id=641711

There are missing exact steps for a reproducer, unfortunately. Note it depends on couple things, like the calendar content, what is the last notification from the given calendar and such.

(In reply to comment #11)
> Opened upstream bug report for the same:
> https://bugzilla.gnome.org/show_bug.cgi?id=641711
> 
> There are missing exact steps for a reproducer, unfortunately.

Well, "Evolution crashed silently in the background" is unhelpful enough to omit it entirely IMO...

One way to reproduce this:

a) Make sure that Edit->Preferences->Calendar and Tasks->Alarms tab,
   [ ] Display alarms in notification area only
   is not checked
b) run /usr/libexec/evolution/2.32/evolution-alarm-notify on a console,
   if not running already
c) in Evolution's Calendar view add a new On This Computer calendar, name
   it anyhow, like 'test', and when created then select it in the left tree
   and make sure it's checked for Alarm notification on the same tab as a)
d) switch to a day view and create a new event with these values:
   Calendar: test
   Summary: alarm 1
   Time: today, not more than 60 minutes from current time
         (like if it's 2:10 PM, then at 2:30 PM)
   Set an alarm on it: 1 hour before the appointment
   [Save]
e) a notification window with the appointment alarm is shown; left it as is
   and switch back to evolution. Create the second alarm event same as the one
   at d), only make the time for it's start one minute later than the alarm 1;
   Name it "alarm 2"
   [Save]
f) a notification for "alarm 2" is shown, the new event is added to the
   previously opened notification window, below the alarm 1
g) in the notification window select "alarm 2" and click "Dismiss";
   the notification window contains only one event now, the "alarm 1".
h) keep the notification window as is and switch to evolution;
   right click the "test" calendar and "Delete" it
i) switch to the notification window and close it with [x] at the right
   top corner (or whenever your window manager shows the button to close
   the window)
The evolution-alarm-notify process crashed at remove_queued_alarm()  with backtrace:

321			qa = l->data;
(gdb) bt
#0  0x0000000000408faa in remove_queued_alarm (cqa=0x66c310, alarm_id=0x66c2e0, free_object=0, remove_alarm=1) at alarm-queue.c:321
#1  0x000000000040a69f in tray_list_remove_async (msg=0x7a9770) at alarm-queue.c:1130
#2  0x0000000000408d9c in message_push (msg=0x7a9770) at alarm-queue.c:183
#3  0x000000000040a792 in tray_list_remove_icons () at alarm-queue.c:1158
#4  0x000000000040aafd in notify_dialog_cb (result=ALARM_NOTIFY_CLOSE, snooze_mins=-1, data=0x6ff520) at alarm-queue.c:1264
#5  0x0000000000407a83 in dialog_response_cb (dialog=0x70c090 [GtkDialog], response_id=4294967292, user_data=0x69e0c0) at alarm-notify-dialog.c:143
#6  0x00000037dda0e2fe in g_closure_invoke (closure=0x7f37d0, return_value=0x0, n_param_values=2, param_values=0x7a28a0, invocation_hint=0x7fffffffd2d0) at gclosure.c:766
#7  0x00000037dda23d85 in signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x70c090, emission_return=0x0, instance_and_params=0x7a28a0) at gsignal.c:3252
#8  0x00000037dda25226 in g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=0x7fffffffd4c0) at gsignal.c:2983
#9  0x00000037dda257e3 in g_signal_emit (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>) at gsignal.c:3040
... (the rest of the backtrace is boring, ends in main().

I added couple more fixes in this one, all related to alarm notify process, kind of regressions from 2.28.3, thus I guess all will be fine. Namely:

   commit 350f7118fec5b5d7bcf6a6c40d2fba6bedaf512e
       Make sure evolution-alarm-notify is running on Evolution's start

   commit 48d30dcad171fe84928ba1888a45f7baa3669bda
       Bug #680611 - Hibernation shifts alarm notification time

   commit 608069630f978c2da37bc57ee58342ba9d16f70f
       Bug #665129 - Memory leak in EBufferTagger

   commit f6f4a73bcf229809c8b4ac13b0b74f8a95a0f67e
       Bug #641711 - Crash in remove_queued_alarm

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1540.html