abrt 1.0.6 detected a crash. architecture: i686 Attached file: backtrace cmdline: python /home/familia/.cedega/.ui/app/classical/main.py component: python executable: /usr/bin/python kernel: 2.6.31.9-174.fc12.i686.PAE package: python-2.6.2-2.fc12 rating: 4 reason: Process was terminated by signal 6 (Aborted) release: Fedora release 12 (Constantine)
Created attachment 394598 [details] File: backtrace
*** Bug 565919 has been marked as a duplicate of this bug. ***
Thank you for reporting this bug. How reproducible is this problem? If you run the program from a terminal, is an error message printed? Looking at the backtrace, it looks like a fatal XError happened in frame 5 of the program's single thread: RenderBadPicture (invalid Picture parameter) Reassigning to xorg-x11 in the hope that the X maintainer will know how to debug this further. Would you be able to copy this file to /usr/lib/debug/usr/lib/libpython2.6.so.1.0-gdb.py and try to get another backtrace please: http://fedorapeople.org/gitweb?p=dmalcolm/public_git/libpython.git;a=blob_plain;f=libpython.py;hb=HEAD (see https://fedoraproject.org/wiki/Features/EasierPythonDebugging for more information)
Created attachment 394637 [details] gdb session while running pychess Not sure if this is related, but I have sometimes been getting RenderBadPicture, various other X-related errors, and sometimes hangs while running pychess. Bug 562471 - pychess may hang gnome desktop I seem to be the only one who can reproduce these. Have reproduced them on a fully updated F12 and on rawhide on two systems: "pychess --sync" and underclocking the CPU seem to make them more reproducible. I copied libpython2.6.so.1.0-gdb.py as suggested in comment 3. The attachment shows two runs of pychess under gdb on F12, the first ended with: pychess: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. and the second with: ... Gdk-ERROR **: The program 'pychess' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 20229 error_code 155 request_code 146 minor_code 7) (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... Program received signal SIGABRT, Aborted. ... There were 20 threads when pychess aborted. (pychess also forks three child processes, but I didn't document those.)
Steve: re comment #4, unfortunately, the -gdb.py file didn't help much: almost all of the data of interest says "<value optimized out>". I do notice that that error happens within a call to gdk_window_x11_set_cursor(NULL) (frame 11 of attachment 394637 [details]), whereas the backtrace for this bug happens within a flush gtk_container_idle_sizer (though maybe it needs a --sync option). I don't know if this is the same issue, but I'm not an expert on X.
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
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.