apport-gtk crashed with SIGABRT in __assert_fail_base()

[Maxim Fam]

apport-gtk crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: apport-gtk 2.4-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
CrashCounter: 1
Date: Tue Jul 31 18:32:36 2012
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
 TERM=unknown
Signal: 6
SourcePackage: apport
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: apport-gtk crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-07-27 (3 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=0xb5f01bb1 <Address 0xb5f01bb1 out of bounds>, assertion=0xb67dce90 "!xcb_xlib_threads_sequence_lost", file=0xb67dd0ea "../../src/xcb_io.c", line=273, function=0xb67dd1d8 "poll_for_event") at assert.c:94
 __GI___assert_fail (assertion=assertion@entry=0xb67dce90 "!xcb_xlib_threads_sequence_lost", file=file@entry=0xb67dd0ea "../../src/xcb_io.c", line=line@entry=273, function=function@entry=0xb67dd1d8 "poll_for_event") at assert.c:103
 poll_for_event (dpy=dpy@entry=0x9e42800) at ../../src/xcb_io.c:270
 poll_for_response (dpy=dpy@entry=0x9e42800) at ../../src/xcb_io.c:288
 _XEventsQueued (dpy=dpy@entry=0x9e42800, mode=mode@entry=2) at ../../src/xcb_io.c:362

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1024202, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.