apport-gtk assert failure: python3: ../../src/xcb_io.c:274: poll_for_event: Asserção `!xcb_xlib_threads_sequence_lost' falhou.

[Antonio Carlos Santos Galvão]

dont know

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: apport-gtk 2.12.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
AssertionMessage: python3: ../../src/xcb_io.c:274: poll_for_event: Asserção `!xcb_xlib_threads_sequence_lost' falhou.
Date: Fri Aug 30 18:23:36 2013
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Signal: 6
SourcePackage: apport
StacktraceTop:
 __assert_fail_base (fmt=0x7f6901fcb89f <Address 0x7f6901fcb89f out of bounds>, assertion=assertion@entry=0x7f68fffb7cd8 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f68fffb7b23 "../../src/xcb_io.c", line=line@entry=274, function=function@entry=0x7f68fffb7fe6 "poll_for_event") at assert.c:92
 __GI___assert_fail (assertion=0x7f68fffb7cd8 "!xcb_xlib_threads_sequence_lost", file=0x7f68fffb7b23 "../../src/xcb_io.c", line=274, function=0x7f68fffb7fe6 "poll_for_event") at assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: apport-gtk assert failure: python3: ../../src/xcb_io.c:274: poll_for_event: Asserção `!xcb_xlib_threads_sequence_lost' falhou.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[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 #1216175, 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.