bamfdaemon assert failure: bamfdaemon: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

[C de-Avillez]

Not sure what happened. I was happily typing away on a IRC session when I got shown the LightDM login screen again.

I have no clue on how to reproduce...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bamfdaemon 0.2.110-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
AssertionMessage: bamfdaemon: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Date: Wed Feb 22 12:15:17 2012
DuplicateOf: https://bugs.launchpad.net/bugs/927727
ExecutablePath: /usr/lib/bamf/bamfdaemon
ProcCmdline: /usr/lib/bamf/bamfdaemon
Signal: 6
SourcePackage: bamf
StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7f4b0b373ad8 "!xcb_xlib_threads_sequence_lost", file=0x7f4b0b373d92 "../../src/xcb_io.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x7f4b0b373ad8 "!xcb_xlib_threads_sequence_lost", file=0x7f4b0b373d92 "../../src/xcb_io.c", line=273, function=0x7f4b0b373eb8 "poll_for_event") at assert.c:103
 poll_for_event (dpy=<optimized out>) at ../../src/xcb_io.c:270
 poll_for_response (dpy=0xa6b430) at ../../src/xcb_io.c:288
 _XEventsQueued (dpy=0xa6b430, mode=<optimized out>) at ../../src/xcb_io.c:362
Title: bamfdaemon assert failure: bamfdaemon: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
UpgradeStatus: Upgraded to precise on 2012-01-13 (40 days ago)
UserGroups: adm admin cdrom dialout kismet kvm libvirtd lpadmin plugdev sambashare sudo vboxusers

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