alacritty
alacritty copied to clipboard
alacritty
XCB aborting
Which operating system does the issue occur on? Linux
If on linux, are you using X11 or Wayland? X11
I get this every now and then when I launch Alacritty.
$ alacritty -v
Welcome to Alacritty.
Configuration loaded from /home/niklas/.config/alacritty.yml
[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.
alacritty: ../../src/xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted
Ah, yes, this issue continues to haunt me: tomaka/winit#458
How common is this for you? I've only ever seen it happen with Alacritty once (and zero times with my own apps), but if it happens to other people on a recurring basis, I'll make fixing this issue more of a priority.
Not that often. Usually i start alacritty with a keyboard shortcut and maybe 1 in 100 it doesn't start. Obviously I cannot be sure that this is the issue. But once or twice it happened when i was running alacritty with -v and could therefore report it. I think it happens more regularly with the -v flag if that makes a difference.
The -v option might just be cause of a racing condition which makes that more likely. Might be interesting to see if it happens more often in debug mode? I don't think -v actually does any functionality stuff that changes things.
winit 0.15.1 is out, so cargo update will hopefully make this problem disappear.
Unfortunately I've just ran into this issue with the latest commit 63a40df5203178bbea1ff1a6988e6d30b6f992f4. On my machine it appears to crash on every third run or so.
However I'm running on Wayland with the command provided in the readme env WAYLAND_DISPLAY= alacritty. Here's the rest of the setup
Fedora 28 Gnome 3.28 Linux 4.18.7-200.fc28.x86_64 libwayland-egl-1.15.0-1.fc28.x86_64
If you need any other info, let me know
@afonso360 Have you tested this with the latest Alacritty version with libxcb installed on your system?
If so I'll reopen this issue. It might need to be fixed in winit/glutin though.
The crash was with libxcb-1.13-1.fc28.x86_64, which appears to be the latest minor release published on the xcb website.
I've now tested with ef06109d94ddb58e0dbc88663eb01f73d1ec8063. Still the same thing.
An interesting thing to note, this crash, does not happen in my laptop, which is running arch, with the same versions of xcb, gnome and the kernel. It does not have libwayland-egl installed
Reopening since it doesn't seem completely fixed yet. However it's probably going to be difficult to figure this out, since it's hard to reproduce.
Also mentioning @francesca64, since she probably knows a lot more about what's going on here than me.
Since updating 6 days ago from 0.7.2 to 0.8.0, I’ve met this issue a few dozens of times, even though I never met it before, that I remember. But I can’t do it on purpose.
Can confirmed this happens often on my machine with X11, nvidia GPU on 5.13.12-arch1-1 running alacritty 0.9.0.
Since recently updating my system, I do not have this issue any more (or at the very least much much less often). alacritty got updated from 0.10.0 to 0.10.1 and libxcb from 1.14 to 1.15.