abrt 1.1.1 detected a crash.
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/pychess
comment: I rotated the chess board.
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Created attachment 430198 [details]
Thanks for the bug report,
it seems, lately, there are many crashes that look similar like this, which indicate a python internal problem...
How relyable can you reproduce this?
Does it happen always, when you rotate the chess board?
(I couldn't reproduce this now...)
Dave, sorry, for forwarding again...
Thank you for reporting this bug.
How reproducible is this problem? If you run the program from a terminal, is an error message printed?
What is the output of running the following command?
rpm -q pygtk2 gtk2
Looking at the backtrace, it looks like a SIGABRT happened in frame 5 of thread #1 inside gdk_x_error:
BadRequest (invalid request code or no such operation)
Reassigning component from "python" to "gtk2"; hopefully the gtk2 maintainer will be able to figure this out further or reassign as necessary.
I could not reproduce the bug. But I deleted all pychess config files and started pychess from terminal.
$ rm -rf .cache/pychess/
$ rm -rf .config/pychess/
$ rm -rf .local/share/pychess/
no stock_draw-rounded-square-unfilled icon in icon-theme-gnome
no stock_draw-rounded-square icon in icon-theme-gnome
/usr/lib/python2.6/site-packages/pychess/System/uistuff.py:374: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
self.glade = gtk.glade.XML(addDataPrefix("glade/%s" % filename))
09:41:01 ('Python', '09:07:1.017') Warning: Chan closed for 'nopost'
09:41:01 ('Python', '09:07:1.017') Warning: Chan closed for '\n'
09:41:30 Default Warning: Chatpanel loaded with two local players
When I load a pgn file, pychess is starts using above 98% cpu continuously. Its not crashing now.
$ rpm -q pygtk2 gtk2
Please reply if you want me do any specific test cases?
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13'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 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.