[Openev-discuss] Gdk errors with project files

[Gillian W. <gil...@at...>]

Hi,

For a while I have been noticing frequent Gdk errors when trying to load
project files in OpenEV on Linux.  The message I get before OpenEV dies
is:

Gdk-ERROR **: BadValue (integer parameter out of range for operation)
  serial 3377 error_code 2 request_code 128 minor_code 13

This error so far only seems to occur when hardware acceleration is used
rather than Mesa.  Unfortunately, the error is also starting to pop up
when windows are shut in applications that use openev.  It seems to crop
up mostly when the first view is destroyed before others are created,
but I don't know enough about OpenGL/gtk/hardware acceleration vs.
software OpenGL to know whether this is a problem with the driver, or a
bug that Mesa deals with gracefully but that the hardware accelerated
version of OpenGL can't deal with.

I recompiled gtk/glib/python/pygtk/gtkglarea etc. with debug mode on and
managed to get a stack trace in gdb:

#0  0x42029331 in kill () from /lib/i686/libc.so.6
#1  0x4202911a in raise () from /lib/i686/libc.so.6
#2  0x4202a8c2 in abort () from /lib/i686/libc.so.6
#3  0x40223c12 in g_logv (log_domain=0x402094d7 "Gdk",
log_level=G_LOG_LEVEL_ERROR,
    format=0x402097c0 "%s\n  serial %ld error_code %d request_code %d
minor_code %d\n", args1=0xbfffbafc) at gmessages.c:391
#4  0x40223cb3 in g_log (log_domain=0x402094d7 "Gdk",
log_level=G_LOG_LEVEL_ERROR,
    format=0x402097c0 "%s\n  serial %ld error_code %d request_code %d
minor_code %d\n") at gmessages.c:408
#5  0x401eb32d in gdk_x_error (display=0x81e5050, error=0xbfffbb90) at
gdk.c:1076
#6  0x4027db4e in _XError () from /usr/X11R6/lib/libX11.so.6
#7  0x4027c1df in _XReply () from /usr/X11R6/lib/libX11.so.6
#8  0x4076a93f in XF86DRICloseFullScreen () from
/usr/X11R6/lib/libGL.so.1
#9  0x4091346c in driMesaUnbindContext () from
/usr/X11R6/lib/modules/dri/radeon_dri.so
#10 0x40756723 in glXMakeCurrent () from /usr/X11R6/lib/libGL.so.1
#11 0x40368c26 in gdk_gl_context_unref (context=0x83f6158) at
gdkgl.c:195
#12 0x403693f6 in gtk_gl_area_destroy (object=0x84288f8) at
gtkglarea.c:169
#13 0x4084ec4d in gv_view_area_destroy (object=0x84288f8) at
gvviewarea.c:3081
#14 0x40146977 in gtk_marshal_NONE__NONE (object=0x84288f8,
func=0x4084eba0 <gv_view_area_destroy>, func_data=0x0,
    args=0xbfffbe40) at gtkmarshal.c:312
#15 0x40179f27 in gtk_signal_real_emit (object=0x84288f8, signal_id=1,
params=0xbfffbe40) at gtksignal.c:1492
#16 0x40177edc in gtk_signal_emit (object=0x84288f8, signal_id=1) at
gtksignal.c:552
#17 0x4015a3b5 in gtk_object_shutdown (object=0x84288f8) at
gtkobject.c:255
#18 0x401b61d5 in gtk_widget_shutdown (object=0x84288f8) at
gtkwidget.c:4390
#19 0x4015a34c in gtk_object_destroy (object=0x84288f8) at
gtkobject.c:246
#20 0x401ae975 in gtk_widget_destroy (widget=0x84288f8) at
gtkwidget.c:1391
(etc...)

Has anyone else encountered this problem?  Any ideas on how to
diagnose/fix it?


Gillian