Red Hat Bugzilla – Bug 1282077
[abrt] evolution: g_quark_init(): evolution killed by SIGABRT
Last modified: 2016-12-20 10:53:47 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#4 g_quark_init at gquark.c:60
#5 glib_init at glib-init.c:236
#6 glib_init_ctor at glib-init.c:287
#7 call_init at dl-init.c:72
#9 _dl_init at dl-init.c:120
#10 dl_open_worker at dl-open.c:564
#11 _dl_catch_error at dl-error.c:187
#12 _dl_open at dl-open.c:649
#13 dlopen_doit at dlopen.c:66
#14 _dl_catch_error at dl-error.c:187
Created attachment 1094148 [details]
Created attachment 1094149 [details]
Created attachment 1094150 [details]
Created attachment 1094151 [details]
Created attachment 1094152 [details]
Created attachment 1094153 [details]
Created attachment 1094154 [details]
Created attachment 1094155 [details]
Created attachment 1094156 [details]
Created attachment 1094157 [details]
Created attachment 1094158 [details]
Thanks for a bug report. The backtrace shows that the application had been stopped in a glib2 code, when it was loading
The error happened in a glib_init() code, with an assertion:
GLib:ERROR:gquark.c:60:g_quark_init: assertion failed: (quark_seq_id == 0)
I do not understand how this could happen, because it was called inside a dedicated thread.
By any chance, are you able to reproduce this after some steps?
I do not see it in the backtrace, but it can happen that the related memory could be overwritten due to some memory issue (some code wrote to a place where it should not) and cause this. As I said, I do not see any good sign of this in the backtrace. I think of bug #1281331, which can be partly related.
I am not able to reproduce this issue, but I just ran into it too.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.