Red Hat Bugzilla – Bug 795135
[abrt] evolution-3.2.3-1.fc16: __GI_raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Last modified: 2013-02-13 13:24:34 EST
libreport version: 2.0.8
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
time: Sun 19 Feb 2012 07:30:12 AM PST
var_log_messages: Feb 19 07:30:13 orpheus abrt: Saved core dump of pid 2194 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2012-02-19-07:30:12-2194 (237514752 bytes)
backtrace: Text file, 46559 bytes
build_ids: Text file, 8364 bytes
dso_list: Text file, 20920 bytes
gconf_subtree: Text file, 18663 bytes
maps: Text file, 98028 bytes
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:** (evolution:28574): DEBUG: Loading Exchange EWS Plugin
:** (evolution:1517): DEBUG: Loading Exchange EWS Plugin
:** (evolution:2194): DEBUG: Loading Exchange EWS Plugin
:evolution-shell-Message: Network disconnected. Forced offline.
:evolution-shell-Message: Connection established. Going online.
:(evolution:2194): camel-ews-provider-WARNING **: Unable to fetch the folder hierarchy: No response: Connection terminated unexpectedly :287
:***MEMORY-ERROR***: evolution: GSlice: assertion failed: sinfo->n_allocated > 0
Created attachment 564191 [details]
Created attachment 564192 [details]
Created attachment 564193 [details]
Created attachment 564194 [details]
Created attachment 564195 [details]
Thanks for a bug report. This is crashing somewhere deep in gtk3 code, due to memory corruption. I'm wondering whether it's related to bug #790190 too. It would be good if you could give to the update from that bug a try.
Backtrace analysis of bugs across components suggests the actual bug might be in component glib2 instead of component gtk3. You might want to inspect the backtraces from the bugs listed below to find out the correct component.
Bugs which were found to be similar to this bug:
evolution: bug #600679
gitg: bug #725717
gnome-settings-daemon: bug #757705
telepathy-idle: bug #625767, bug #627434
This comment is automatically generated.
*** Bug 757705 has been marked as a duplicate of this bug. ***
*** Bug 725717 has been marked as a duplicate of this bug. ***
Just tried to rebase two branches in git.
OS Release: Fedora release 16 (Verne)
Created attachment 582791 [details]
With gitg open, switched branches in the git repository which I was viewing. gitg then crashed without me even touching it.
OS Release: Fedora release 17 (Beefy Miracle)
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora
'version' of '16'.
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 prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 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 to click on
"Clone This Bug" and open it against that version of Fedora.
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.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.
Thank you for reporting this bug and we are sorry it could not be fixed.