Version-Release number of selected component: evolution-3.28.2-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/evolution/evolution-alarm-notify crash_function: magazine_chain_pop_head executable: /usr/libexec/evolution/evolution-alarm-notify journald_cursor: s=3d9aa17c4f9e40d0924888316191a2e2;i=1fd6;b=337ee2b697e34f118486bb1b1a3604ed;m=18e9d98;t=56e94ddbf769c;x=122606d66486bbd6 kernel: 4.16.14-300.fc28.x86_64 rootdir: / runlevel: N 5 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:1016 #3 g_ptr_array_sized_new at garray.c:915 #4 g_ptr_array_new at garray.c:896 #5 g_main_context_new at gmain.c:652 #6 g_dbus_connection_send_message_with_reply_sync at gdbusconnection.c:2138 #7 g_dbus_connection_call_sync_internal at gdbusconnection.c:5950 #8 g_dbus_connection_call_with_unix_fd_list_sync at gdbusconnection.c:6299 #9 g_dbus_proxy_call_sync_internal at gdbusproxy.c:2870 Potential duplicate: bug 979186
Created attachment 1451156 [details] File: backtrace
Created attachment 1451157 [details] File: cgroup
Created attachment 1451158 [details] File: core_backtrace
Created attachment 1451159 [details] File: cpuinfo
Created attachment 1451160 [details] File: dso_list
Created attachment 1451161 [details] File: environ
Created attachment 1451162 [details] File: exploitable
Created attachment 1451163 [details] File: limits
Created attachment 1451164 [details] File: maps
Created attachment 1451165 [details] File: mountinfo
Created attachment 1451166 [details] File: open_fds
Created attachment 1451167 [details] File: proc_pid_status
Thanks for a bug report. I do not see much from the backtrace, just that it crashed when the application had been opening certain calendar (or task list or memo list), but nothing more from it. There seems to be some memory corruption involved, maybe some code accessed part of memory which had been freed or uninitialized, which could happen long before, like during start of the application. By any chance, are you able to reproduce this, please? Eventually do you know what had been happening in the application before the crash, please? It can involve things like selecting a meeting invitation email, adding new calendar, selecting a calendar to include it in the view and so on.
Similar problem has been detected: The crash happened after lunching Evolution in a virtual machine and entering the user credentials, probably while auto-detecting the account properties. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: evolution crash_function: magazine_chain_pop_head executable: /usr/bin/evolution journald_cursor: s=6630c9e37c99414ab2d0d9f807a4ed6a;i=8c40;b=0aca222be7c643aeaef14c6c1bafb934;m=2dc50896;t=57c6f54d63c86;x=86fa486110a30a75 kernel: 4.19.6-200.fc28.x86_64 package: evolution-3.28.5-2.fc28 reason: evolution killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.