abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: python -u /home/eddie/.screenlets/CPU_Meter/CPU_MeterScreenlet.py component: python executable: /usr/bin/python kernel: 2.6.32.9-70.fc12.i686.PAE package: python-2.6.2-4.fc12 rating: 4 reason: Process /usr/bin/python was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine)
Created attachment 404194 [details] File: backtrace
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 cairo pygtk2 gtk2 Looking at the backtrace, it looks like an assertion failed inside frame 3 of the program's single thread inside _XAllocID, and it appears to be a pygtk2 application. Reassigning component from "python" to "gtk2"; hopefully the gtk2 maintainer will be able to figure this out further or reassign as necessary.
rpm -q cairo pygtk2 gtk2 produces: cairo-1.8.8-3.fc12.i686 pygtk2-2.16.0-1.fc12.i686 gtk2-2.18.9-2.fc12.i686 It is not very reproducible, the error only appears now and then. I most certainly do not know how to reproduce it. Launching the app by hand does not reveal any useful information. On the other side, it is not a major issue. I have not seen it since 30th of march. I have a few screenlets running that are started automatically and I think the error is being generated when I log out or shutdown the system while these screenlets still are running.
Segfaults involving _XAllocID go to libxcb