GTK+ applications crash with error_code 2 request_code 146 minor_code 5 Similarity with message: http://lists.freedesktop.org/archives/xorg/2009-June/046143.html and bug #22392: http://bugs.freedesktop.org/show_bug.cgi?id=22392
Created attachment 30653 [details] zenity gdb backtrace a thin backtrace example of zenity
Created attachment 30654 [details] gtkmm-demo gdb backtrace thin backrace of gtkmm-demo crash
narrowed buggy git updates to: libX11, libXext, xorg-server, libdrm, mesa, cairo xterm etc. and QT3/QT4 work perfect unaffected. pygtk based windows crash lazyon first mouse click (synaptics).
narrowed buggy git updates to: libX11, libXext, xorg-server, libdrm, mesa, cairo xterm etc. and QT3/QT4 work perfect unaffected. pygtk based apps crash at first mouse click (synaptics).
(In reply to comment #0) > GTK+ applications crash with error_code 2 request_code 146 minor_code 5 Request codes > 128 indicate an X extension. Unfortunately, GTK's broken X error handler discards the information about which extension that is, and the mapping of extension to request code is dynamic based on which extensions are active in your server (based on build time & run time configurations). To find out which one 146 is on your system, run: xdpyinfo -query | grep 'opcode: 146'
(In reply to comment #5) > > To find out which one 146 is on your system, run: > xdpyinfo -query | grep 'opcode: 146' > It's RENDER and it's "sytstems" :) With "RENDER" extension "off", the cursor is white, but no crashes with gtk+ applications. Xorg/libX11/libXext/libXrender is installed from git on several systems.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.