glutin: Assertion `!xcb_xlib_threads_sequence_lost' failed

Trying to run on Ubuntu 14.04

kuviman@UbuntuBox:~/Temp/glutin$ cargo run --example window
    Finished dev [unoptimized + debuginfo] target(s) in 0.21s
     Running `target/debug/examples/window`
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
window: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 4
Comments: 22 (13 by maintainers)

Most upvoted comments

This is unfortunate, but our patch got reverted due to breaking wine applications: https://bugs.freedesktop.org/show_bug.cgi?id=110632

goddessfreya on Jun 21, 2019

https://gitlab.freedesktop.org/mesa/mesa/merge_requests/523

goddessfreya on Mar 26, 2019

According to the folks at #xorg-devel (Thanks DrNick), we’ve rediscovered https://bugs.freedesktop.org/show_bug.cgi?id=99781

goddessfreya on Mar 23, 2019

I’m encountering this issue too. I’m using the newest Xubuntu (21.10) with X11 and Mesa (21.2.2), but use i3 as a window manager.

As a test, I ran the basic window example (https://github.com/rust-windowing/glutin/blob/master/glutin_examples/examples/window.rs), using glutin 0.28.0, in a loop n times.

It (almost) always fails under i3. Success: 5/100.
I also tried i3 with a compositor (compton and picom with default settings), but didn’t notice any improvements.
It always works under xfce. Success: 30/30.

Note that the crash never happens on another machine that also runs i3 but uses NVIDIA drivers.

So at least for me, this bug is also related to the desktop environment / window manager. I think future reports should include this info.

markus-bauer on Jan 8, 2022

Patch has been merged. Next version of mesa will fix this!

goddessfreya on Apr 30, 2019