Hide Forgot
Version-Release number of selected component: evolution-3.22.1-2.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: evolution crash_function: magazine_chain_pop_head executable: /usr/bin/evolution global_pid: 2924 kernel: 4.8.7-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project 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_slice_alloc0 at gslice.c:1051 #4 g_source_new at gmain.c:916 #5 g_timeout_source_new_seconds at gmain.c:4734 #6 g_timeout_add_seconds_full at gmain.c:4919 #7 camel_sqlite3_file_xSync at camel-db.c:325 #8 sqlite3PagerCommitPhaseOne at sqlite3.c:52610 #9 sqlite3BtreeCommitPhaseOne at sqlite3.c:61880 Potential duplicate: bug 979186
Created attachment 1222768 [details] File: backtrace
Created attachment 1222769 [details] File: cgroup
Created attachment 1222770 [details] File: core_backtrace
Created attachment 1222771 [details] File: dso_list
Created attachment 1222772 [details] File: environ
Created attachment 1222773 [details] File: exploitable
Created attachment 1222774 [details] File: limits
Created attachment 1222775 [details] File: maps
Created attachment 1222776 [details] File: mountinfo
Created attachment 1222777 [details] File: namespaces
Created attachment 1222778 [details] File: open_fds
Created attachment 1222779 [details] File: proc_pid_status
Created attachment 1222780 [details] File: var_log_messages
Thanks for a bug report. I do not recall seeing any similar crash in the recent past, though the backtrace suggests that this was caused by some kind of memory corruption, most likely some code accessing already freed memory and writing to it. Such issues is pretty hard to reproduce, usually. They also usually strike in various places, not in exactly one. By any chance, do you recall what preceded to this crash, please?
Unfortunately, I do not have any steps to reproduce as ABRT reported this crash when Evolution was not even running at this time. I had this crash happen before on Fedora 25 when it was running but also in that case I also did not do anything specific that I could reproduce. I'll pay close attention going forward in hope to be able to trigger this more reliably on my system.
Similar problem has been detected: evolution-alarm-notify crashed on startup right after logging in. reporter: libreport-2.8.0 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: 2012 kernel: 4.8.15-300.fc25.x86_64 package: evolution-3.22.3-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: evolution-alarm-notify killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.