Red Hat Bugzilla – Bug 1013457
[abrt] evince-3.8.3-2.fc19: gtk_container_accessible_remove_gtk: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Last modified: 2015-06-29 08:29:51 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 gtk_container_accessible_remove_gtk at gtkcontaineraccessible.c:101
#5 gtk_container_remove at gtkcontainer.c:1546
#6 gtk_widget_dispose at gtkwidget.c:10760
#8 ev_view_forall at ev-view.c:4793
#9 gtk_container_destroy at gtkcontainer.c:1377
#14 gtk_widget_dispose at gtkwidget.c:10771
#16 gtk_scrolled_window_forall at gtkscrolledwindow.c:1582
#17 gtk_container_destroy at gtkcontainer.c:1377
#22 gtk_widget_dispose at gtkwidget.c:10771
#24 gtk_overlay_forall at gtkoverlay.c:583
Created attachment 804910 [details]
Created attachment 804911 [details]
Created attachment 804912 [details]
Created attachment 804913 [details]
Created attachment 804914 [details]
Created attachment 804915 [details]
Created attachment 804916 [details]
Created attachment 804917 [details]
Created attachment 804918 [details]
Created attachment 804919 [details]
Created attachment 804920 [details]
Created attachment 869709 [details]
The crash happens if a field in a fillable form is selected by mouse and then the document is closed by Ctrl-W. Open the attached form in evince, select the field to the right of "tax year" and press Ctrl-W. evince would crash every time.
I think that this is a problem in GTK+ itself. I've prepared a patch for it and attached it to the bug https://bugzilla.gnome.org/show_bug.cgi?id=725733.
I'm reassigning this to GTK+
Thank you, Marek! I rebuilt gtk3 with your patch, and evince in not crashing on the attached example file anymore.
Created attachment 871726 [details]
Patch by Marek Kašík
Successfully tested on Fedora 20 by rebuilding gtk3.
You have blocked SIMPLE_PATCHES. Please follow the procedure described in here: https://fedoraproject.org/wiki/Policy_for_simple_patches
(In reply to Miro Hrončok from comment #16)
> You have blocked SIMPLE_PATCHES. Please follow the procedure described in
> here: https://fedoraproject.org/wiki/Policy_for_simple_patches
My Koji account is broken or doesn't have sufficient privileges. It refuses to build anything for me:
*** Bug 1111900 has been marked as a duplicate of this bug. ***
The patch doesn't apply to recent versions of gtk. Evince doesn't crash on Ctrl-W in text entry field anymore (up to date Fedora 21 x86_64, gtk3-3.14.9-1). I believe this bug can be closed.
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'
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
Thank you for reporting this bug and we are sorry it could not be fixed.