Red Hat Bugzilla – Bug 868464
[abrt] python-2.7.3-7.2.fc17: INT_cairo_set_line_width: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-31 19:56:07 EDT
Description of problem:
I have an application, gtg as of 2012-10-20 in this case, in conjunction with liblarch, which crashes.
Based on the stackstrace, I think that the engine is the culprit. I might be totally mistaken though.
But after "sudo mv /usr/lib64/gtk-2.0/2.10.0/engines/libclearlooks.so /tmp/" it started.
To reproduce, do
bzr branch lp:gtg trunk
and run ./gtg
it will fetch liblarch.
$ python gtg --no-crash-handler
2012-10-20 02:44:21,797 - WARNING - __init__:__init__:77 - Backend backend_launchpad could not be loaded: No module named launchpadlib.launchpad
2012-10-20 02:44:21,799 - WARNING - __init__:__init__:77 - Backend backend_mantis could not be loaded: No module named suds.client
2012-10-20 02:44:22,151 - ERROR - engine:_load_module:135 - name 'appindicator' is not defined
/home/muelli/hg/gtg.bzr/trunk/GTG/gtk/manager.py:283: Warning: cannot register existing type `GdkWindow'
/home/muelli/hg/gtg.bzr/trunk/GTG/gtk/manager.py:283: Warning: g_once_init_leave: assertion `result != 0' failed
/home/muelli/hg/gtg.bzr/trunk/GTG/gtk/manager.py:283: GtkWarning: gdk_cairo_create: assertion `GDK_IS_WINDOW (window)' failed
Segmentation fault (core dumped)
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: python gtg --no-crash-handler
:Thread no. 1 (10 frames)
: #0 INT_cairo_set_line_width at cairo.c:1205
: #1 ge_gdk_drawable_to_cairo at ./cairo-support.c:286
: #2 clearlooks_style_draw_box at src/clearlooks_style.c:507
: #3 gtk_toolbar_expose at gtktoolbar.c:874
: #4 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
: #9 gtk_widget_event_internal at gtkwidget.c:4999
: #10 gtk_widget_send_expose at gtkwidget.c:4828
: #11 gtk_container_propagate_expose at gtkcontainer.c:2757
: #12 gtk_box_forall at gtkbox.c:1251
: #13 gtk_container_expose at gtkcontainer.c:2661
Created attachment 630300 [details]
Created attachment 630301 [details]
Created attachment 630302 [details]
Created attachment 630303 [details]
Created attachment 630304 [details]
Created attachment 630305 [details]
Created attachment 630306 [details]
Created attachment 630307 [details]
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.