Bug 579089
Summary: | "_XAllocID: Assertion `ret != inval_id' failed." inside XCreatePixmap running /home/eddie/.screenlets/CPU_Meter/CPU_MeterScreenlet.py | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eddie Lania <eddie> | ||||
Component: | libxcb | Assignee: | Adam Jackson <ajax> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 12 | CC: | ajax, dmalcolm, ivazqueznet, james.antill, jonathansteffan, mclasen | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:23e624d94d172a52c0da18422613574ca580e457 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-07-05 06:34:33 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
Eddie Lania
2010-04-02 15:04:47 UTC
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 |