abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: python /usr/lib/gdesklets/gdesklets-daemon component: gdesklets crash_function: raise executable: /usr/bin/python global_uuid: ee58aacf87d7a80d99bb7e91d527894810754252 kernel: 2.6.33.5-112.fc13.i686.PAE package: gdesklets-0.36.2-2.fc13 rating: 4 reason: Process /usr/bin/python was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard)
Created attachment 423711 [details] File: backtrace
Hmm, apparently python bug. I am going to assign to Dave if he can investigate the problem.
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 gtk2 libxcb Looking at the backtrace, it looks like an assertion failed inside frame 3 of the program's single thread inside _XAllocID: python: xcb_io.c:385: _XAllocID: Assertion `ret != inval_id xcb is failing to allocate a graphic-rendering context for some reason, and that's why the process exits. Reassigning component from "python" to "libxcb"; hopefully the libxcb maintainer will be able to figure this out further or reassign to a more appropriate component.
abrt backtrace doesn't tell me libX11 or libxcb versions, can't really help with this.