Description of problem: Not sure. Possibly happened after coming out of suspend or network reconnection or something like that. Version-Release number of selected component: evolution-3.28.5-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: evolution crash_function: magazine_cache_push_magazine executable: /usr/bin/evolution journald_cursor: s=a3de63a3666b4c369f5158789e3feb95;i=51a6;b=02dde2792e3145c3ae8c35f93bfe3f3c;m=3ad69ebb71;t=5769a41c47765;x=425acb7ada3a76a7 kernel: 4.18.5-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 magazine_cache_push_magazine at gslice.c:700 #1 thread_memory_magazine2_unload at gslice.c:1118 #2 g_slice_free1 at gslice.c:1118 #3 handler_unref_R at gsignal.c:702 #5 g_object_real_dispose at gobject.c:1048 #7 gtk_box_forall at gtkbox.c:2671 #8 gtk_container_destroy at gtkcontainer.c:1700
Created attachment 1486952 [details] File: backtrace
Created attachment 1486953 [details] File: cgroup
Created attachment 1486954 [details] File: core_backtrace
Created attachment 1486955 [details] File: cpuinfo
Created attachment 1486956 [details] File: dso_list
Created attachment 1486957 [details] File: environ
Created attachment 1486958 [details] File: exploitable
Created attachment 1486959 [details] File: limits
Created attachment 1486960 [details] File: maps
Created attachment 1486961 [details] File: mountinfo
Created attachment 1486962 [details] File: open_fds
Created attachment 1486963 [details] File: proc_pid_status
Thanks for a bug report. If I read it properly, then this happened after Evolution noticed the network is online and it finished all the preparations for the online state. This is done after resume from suspend too, thus it can be just as you said. I do not see from the backtrace why exactly the crash happened. There might be involved some memory corruption, possibly some part of the code wrote into an already freed memory or something like that, which is usually pretty hard to reproduce and which can happen on various places (depending what the affected part of the memory had been used for), thus even if the conditions had been reproduced, the actual issue can be triggered long time after it. Was this for the first time you've got this crash, please? If it's as I outlined above, I guess you do not have any steps to reproduce this reliably, right? That's okay if not.
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.