Bug 563714

Summary: [abrt] crash in pychess-0.10-0.1.20100203svn.fc12
Product: [Fedora] Fedora Reporter: Steve Tyler <stephent98>
Component: pychessAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: michel, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:6f5df36e2da1524a6574a96cc1879c6a4d46adf5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 22:59:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: comment none

Description Steve Tyler 2010-02-10 22:22:11 UTC
abrt 1.0.6 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/pychess
Attached file: comment
component: pychess
executable: /usr/bin/python
kernel: 2.6.31.12-174.2.3.fc12.i686
package: pychess-0.10-0.1.20100203svn.fc12
rating: 4
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

How to reproduce
-----
This happened on my laptop while playing chess, enabling/disabling display of hint/spy arrows, resizing/rearranging side panels/window.

Notes:
Did not remove .pychessconf and .pychess/ before starting.
Started this from the command line ... text to follow.
Analyzers were running. After the crash, they were still running and still consuming 100% of the CPU!

Comment 1 Steve Tyler 2010-02-10 22:22:14 UTC
Created attachment 390127 [details]
File: backtrace

Comment 2 Steve Tyler 2010-02-10 22:22:16 UTC
Created attachment 390128 [details]
File: comment

Comment 3 Steve Tyler 2010-02-10 22:28:21 UTC
(In reply to comment #2)
> Created an attachment (id=390128) [details]
> File: comment   

=====
Gdk-ERROR **: The program 'pychess' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 101438 error_code 14 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted (core dumped)
=====

See also:
Bug 562471 -  pychess may hang gnome desktop

Comment 4 Steve Tyler 2010-02-10 22:44:10 UTC
See also (which happened at the same time):
Bug 563720 -  [abrt] crash in pychess-0.10-0.1.20100203svn.fc12

Comment 5 Bug Zapper 2010-11-03 22:27:24 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2010-12-03 22:59:37 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.