After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674465 - gtk3 does not work with xcb-less libx11
gtk3 does not work with xcb-less libx11
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Backend: X11
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-04-20 11:24 UTC by Lauri Kasanen
Modified: 2014-09-08 03:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Backtrace when breaking on gdk_x_error (2.11 KB, text/plain)
2012-04-25 13:13 UTC, Lauri Kasanen
Details

Description Lauri Kasanen 2012-04-20 11:24:59 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.)
Comment 1 Lauri Kasanen 2012-04-20 13:23:00 UTC
Confirmed for gtk 3.4.1 too.
Comment 2 Matthias Clasen 2012-04-25 04:08:41 UTC
We don't use X from multiple threads, no. 
A stacktrace would be helpful.
Comment 3 Lauri Kasanen 2012-04-25 13:13:22 UTC
Created attachment 212778 [details]
Backtrace when breaking on gdk_x_error
Comment 4 Lauri Kasanen 2012-04-25 13:14:42 UTC
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 ;)
Comment 5 Matthias Clasen 2014-09-08 03:13:46 UTC
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.