apport-gtk crashed with SIGABRT in __GI___assert_fail()

[Dimiter "Arruor" Nikov]

Strange behaviour not only for apport-gtk, but for my entire system.
Is not only this application which crashes with 'SIGABRT in raise()'

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic-pae 3.2.1
Uname: Linux 3.2.0-9-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Fri Jan 20 09:38:22 2012
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
Signal: 6
SourcePackage: apport
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () 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
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: apport-gtk crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio backup cdrom dialout lpadmin plugdev root sambashare vboxusers video www-data

[Apport retracing service (apport)]

StacktraceTop:
 __GI___assert_fail (assertion=0xb6464130 "!xcb_xlib_threads_sequence_lost", file=0xb646438a "../../src/xcb_io.c", line=273, function=0xb6464478 "poll_for_event") at assert.c:81
 poll_for_event (dpy=0x8a0d268) at ../../src/xcb_io.c:270
 poll_for_response (dpy=0x8a0d268) at ../../src/xcb_io.c:288
 _XEventsQueued (dpy=0x8a0d268, mode=2) at ../../src/xcb_io.c:362
 XPending (dpy=0x8a0d268) at ../../src/Pending.c:55

[Launchpad Janitor (janitor)]

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

[Martin Pitt (pitti)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 901675, so it 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.