Version-Release number of selected component: evolution-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: evolution crash_function: _g_log_abort executable: /usr/bin/evolution kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #2 _g_log_abort at gmessages.c:255 #5 g_main_context_acquire at gmain.c:3132 #8 gtk_main at gtkmain.c:1158
Created attachment 854093 [details] File: backtrace
Created attachment 854094 [details] File: cgroup
Created attachment 854095 [details] File: core_backtrace
Created attachment 854096 [details] File: dso_list
Created attachment 854097 [details] File: environ
Created attachment 854098 [details] File: limits
Created attachment 854099 [details] File: maps
Created attachment 854100 [details] File: open_fds
Created attachment 854101 [details] File: proc_pid_status
Created attachment 854102 [details] File: var_log_messages
Thanks for a bug report. I see from the backtrace that evolution was aborted due to GLib's assertion: assertion failed: (context->owner_count == 0) while before that happened you restored evolution settings from a backup, while after about 20 minutes later something failed: > (evolution:4005): GLib-CRITICAL **: g_main_context_push_thread_default: > assertion 'acquired_context' failed (the above message is in var_log_messages twice). This, most likely, led to the failed assertion. By any chance, do you have anything more detailed, like certain steps, for a reproducer, please?
I will have to watch for you and hope it happens again. ATM I don't have anything more specific for this particular problem.
Another user experienced a similar problem: I tried to create a task reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: evolution crash_function: _g_log_abort executable: /usr/bin/evolution kernel: 3.15.10-200.fc20.x86_64 package: evolution-3.10.4-3.fc20 reason: evolution killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.