FS#69295 - [libx11] Xlib: sequence lost
Attached to Project:
Arch Linux
Opened by N.T. (NikTo) - Monday, 11 January 2021, 21:57 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 06 January 2023, 21:52 GMT
Opened by N.T. (NikTo) - Monday, 11 January 2021, 21:57 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 06 January 2023, 21:52 GMT
|
Details
Description:
Run any GUI application from terminal emulator in Xorg X11 regardless of window manager. And you will see... Xlib: sequence lost (0x10137 > 0x139) in reply type 0x0! Xlib: sequence lost (0x1013e > 0x140) in reply type 0x0! Xlib: sequence lost (0x10145 > 0x147) in reply type 0x0! Xlib: sequence lost (0x10156 > 0x158) in reply type 0x0! Xlib: sequence lost (0x1015d > 0x15f) in reply type 0x0! Xlib: sequence lost (0x10164 > 0x166) in reply type 0x0! Xlib: sequence lost (0x1016e > 0x170) in reply type 0x0! Xlib: sequence lost (0x10175 > 0x177) in reply type 0x0! ... Additional info: * package version - 1.7.0-3; * tested in awesomewm and spectrwm. |
This task depends upon
But if in doubt - open a bug with the respective project using Xlib.
Definitely not a packaging bug :-)
Keyboard in GDM on Xorg / X11 becomes rapidly unusable (a few seconds after launch of client app) and client app needs to be hard closed and reopened...
Example of journalctl message is "gnome-terminal-server[...]: Xlib: sequence lost (0x10000 > 0x<code>) in reply type 0x2!"