GNOME Bugzilla – Bug 674465
gtk3 does not work with xcb-less libx11
Last modified: 2014-09-08 03:13:46 UTC
In TinyCore we currently ship libx11 1.3.6 (the last version that builds without xcb). It appears that gtk3 3.2.2 uses xlib from multiple threads, thus crashing with an xcb-less libx11. I was told at #gtk+ that things should still work without xcb. -- Output from gtk3-demo: tc@box:~$ gtk3-demo Xlib: sequence lost (0x10223 > 0x2a3) in reply type 0x0! .... a lot of xlib: sequence Xlib: sequence lost (0x10000 > 0x2e3) in reply type 0x0! (gtk3-demo:10234): Gdk-WARNING **: The program 'gtk3-demo' received an X Window System error. This probably reflects a bug in the program. The error was '60'. (Details: serial 26102 error_code 60 request_code 0 minor_code 26) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Confirmed for gtk 3.4.1 too.
We don't use X from multiple threads, no. A stacktrace would be helpful.
Created attachment 212778 [details] Backtrace when breaking on gdk_x_error
Attaching backtrace when breaking on gdk_x_error and starting gtk3-demo with "--sync". Please note that only gtk 3.4.1 was recompiled with debug symbols, if you need glib or something else please say. Just that I'd rather not rebuid libX11 ;)
I don't think there is much hope that we'll invest time into figuring out what is going wrong here - if you are still intested in this problem and have further information to add, feel free to reopen the bug.