Version-Release number of selected component: evolution-3.18.1-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/evolution/evolution-alarm-notify crash_function: magazine_chain_pop_head executable: /usr/libexec/evolution/evolution-alarm-notify global_pid: 2068 kernel: 4.2.5-300.fc23.x86_64 runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:539 #1 thread_memory_magazine1_alloc at gslice.c:842 #2 g_slice_alloc at gslice.c:998 #3 g_ptr_array_sized_new at garray.c:900 #4 g_ptr_array_new at garray.c:881 #5 g_main_context_new at gmain.c:649 #6 g_dbus_connection_send_message_with_reply_sync at gdbusconnection.c:2134 #7 g_dbus_connection_call_sync_internal at gdbusconnection.c:5930 #8 g_dbus_connection_call_with_unix_fd_list_sync at gdbusconnection.c:6276 #9 g_dbus_proxy_call_sync_internal at gdbusproxy.c:2852 Potential duplicate: bug 979186
Created attachment 1093674 [details] File: backtrace
Created attachment 1093675 [details] File: cgroup
Created attachment 1093676 [details] File: core_backtrace
Created attachment 1093677 [details] File: dso_list
Created attachment 1093678 [details] File: environ
Created attachment 1093679 [details] File: exploitable
Created attachment 1093680 [details] File: limits
Created attachment 1093681 [details] File: maps
Created attachment 1093682 [details] File: mountinfo
Created attachment 1093683 [details] File: open_fds
Created attachment 1093684 [details] File: proc_pid_status
Thanks for a bug report. The threads 7 to 2, inclusive, in the backtrace look odd. The crashing thread crashes in a place which is usually tight to a memory corruption of some sort (like the code using already freed memory or something like that). By any chance, do you know what to do to cause the crash, please? As this is in the alarm notify, it might not be necessary anything you did, but rather some queued alarms getting in a state of being reminded. The backtrace itself suggests that the crash happened at the very start of the application, when it was opening the calendars.
Another user experienced a similar problem: Abrt displayed the notify about this crash after the login into a Gnome+Wayland session. However, it's the first time I see it: I'm also unable to reproduce it. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/evolution/evolution-alarm-notify crash_function: magazine_chain_pop_head executable: /usr/libexec/evolution/evolution-alarm-notify global_pid: 2280 kernel: 4.2.6-301.fc23.x86_64 package: evolution-3.18.2-1.fc23 reason: evolution-alarm-notify killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
(In reply to Milan Crha from comment #12) > By any chance, do you know what to do to cause the crash, please? As this is > in the alarm notify, it might not be necessary anything you did, but rather > some queued alarms getting in a state of being reminded. The backtrace > itself suggests that the crash happened at the very start of the > application, when it was opening the calendars. Yesterday I had an event planned for 20.00 o' clock. At that time, I've probably skipped/denied it: today I encountered this bug.
*** Bug 1283735 has been marked as a duplicate of this bug. ***
*** Bug 1323849 has been marked as a duplicate of this bug. ***
*** Bug 1376072 has been marked as a duplicate of this bug. ***
*** Bug 1377043 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.