Bug 24711

Summary: BadValue SIGTRAP g_logv [gtk+/glib/pango<->Xorg] crashes
Product: xorg Reporter: Sebastian Glita <gseba>
Component: * OtherAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium Keywords: regression
Version: unspecified   
Hardware: Other   
OS: All   
URL: http://xorg.freedesktop.org
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
zenity gdb backtrace
none
gtkmm-demo gdb backtrace none

Description Sebastian Glita 2009-10-24 05:31:04 UTC
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
Comment 1 Sebastian Glita 2009-10-24 05:32:54 UTC
Created attachment 30653 [details]
zenity gdb backtrace

a thin backtrace example of zenity
Comment 2 Sebastian Glita 2009-10-24 05:35:18 UTC
Created attachment 30654 [details]
gtkmm-demo gdb backtrace

thin backrace of gtkmm-demo crash
Comment 3 Sebastian Glita 2009-10-24 07:56:02 UTC
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).
Comment 4 Sebastian Glita 2009-10-24 07:57:14 UTC
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).
Comment 5 Alan Coopersmith 2009-10-24 09:15:59 UTC
(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'
Comment 6 Sebastian Glita 2009-10-26 07:02:19 UTC
(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.