Red Hat Bugzilla – Bug 825398
[abrt] anjuta-3.2.0-1.fc16: gtk_widget_child_notify: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
Last modified: 2013-04-30 18:56:00 EDT
libreport version: 2.0.8
reason: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
time: Wed 23 May 2012 06:50:19 PM CDT
backtrace: Text file, 31930 bytes
build_ids: Text file, 5207 bytes
dso_list: Text file, 12663 bytes
maps: Text file, 63178 bytes
:Open project. Intermittently when clicking an x to close an opened document, the segfault occurs. When it happens, if that document was open during last project save so it opens again at project time, it will segfault next time the page is closed by clicking X or close document menu command. Only way to close document once this happens is to then use Close All Documents menu command or hand edit the anjuta project files.
:I have only seen this occur in single makefile, multiple sub-directory projects opened in anjuta, though it may also be just that my larger projects fall into this category.
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:May 23 14:29:37 lloydbal1 anjuta: Ignoring attempt to re-initialize GDA library.
:May 23 18:06:32 lloydbal1 kernel: [15529.128936] anjuta: segfault at 30b ip 00000030a327d7e0 sp 00007fff9e704e08 error 4 in libgtk-3.so.0.200.4[30a3000000+43b000]
:May 23 18:06:37 lloydbal1 abrt: Saved core dump of pid 2465 (/usr/bin/anjuta) to /var/spool/abrt/ccpp-2012-05-23-18:06:32-2465 (183046144 bytes)
:May 23 18:50:19 lloydbal1 kernel: [18152.834665] anjuta: segfault at 30b ip 00000030a327d7e0 sp 00007fffdd48bd78 error 4 in libgtk-3.so.0.200.4[30a3000000+43b000]
:May 23 18:50:21 lloydbal1 abrt: Saved core dump of pid 29300 (/usr/bin/anjuta) to /var/spool/abrt/ccpp-2012-05-23-18:50:19-29300 (143986688 bytes)
Created attachment 586960 [details]
Created attachment 586961 [details]
Created attachment 586962 [details]
Created attachment 586963 [details]
I believe that could be a duplicate of the issue of bug #801403 which has been fixed with anjuta 3.4.1. Can you try the latest version 3.4.2 and tell us if the problem still occurs?
Commits that might be related:
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.