Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 587245 - transmission-gtk-1.92-1.fc12 crashed in clearlooks_gummy_draw_progressbar_fill(): "xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed"
Summary: transmission-gtk-1.92-1.fc12 crashed in clearlooks_gummy_draw_progressbar_fil...
Keywords:
Status: CLOSED DUPLICATE of bug 582438
Alias: None
Product: Fedora
Classification: Fedora
Component: transmission
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e0b84088cad8a6e81e09d4f1ea0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-29 13:17 UTC by sergeobelare
Modified: 2010-04-29 15:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-29 15:02:14 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (31.59 KB, text/plain)
2010-04-29 13:17 UTC, sergeobelare 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description sergeobelare 2010-04-29 13:17:24 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/transmission
comment: Probably related to kernel crash after update to compat-wireless-2.6.32.11
component: transmission
executable: /usr/bin/transmission
global_uuid: e0b84088cad8a6e81e09d4f1ea052c4cff21a413
kernel: 2.6.32.11-99.fc12.i686
package: transmission-gtk-1.92-1.fc12
rating: 4
reason: Process /usr/bin/transmission was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.Unsure
2.
3.
Comment 1 sergeobelare 2010-04-29 13:17:26 UTC 
Created attachment 410103 [details]
File: backtrace
Comment 2 Charles Kerr 2010-04-29 15:02:14 UTC 

*** This bug has been marked as a duplicate of bug 582438 ***
Note You need to log in before you can comment on or make changes to this bug.