Re: [xine-devel] Xlib: unexpected async reply

[Daniel Caujolle-B. <seg...@cl...>]

Hi Bastien,

Le lun 21/04/2003 à 21:09, Bastien Nocera a écrit :
> On Mon, 2003-04-21 at 19:56, Bastien Nocera wrote:
> > Heya,
> > 
> > I'm having some troubles with Totem.
> > 
> > I redesigned the video widget in totem a couple of months ago, using gdk
> > to provide me with X events, and letting the video output handle the
> > completion event (or a thread very early on).
> > 
> > The video widget has 2 connections to X via 2 different displays. One
> > for Gtk+/Gdk, one for the video output.
> > 
> > It works very well, but when I bombard the xine engine with
> > xine_gui_send_vo_data() calls, it craps itself with the error in the
> > subject.
> > 
> > So here are 2 questions:
> > 1) why is xine_gui_send_vo_data() not locked in any way?
> > 2) does anyone know how to better diagnose the problem?
> > 
> > (The reason why I use 2 different connections to the X server is to
> > avoid having to lock every single call to X or gdk that I would make
> > outside the widget).
> 
> It seems that I needed to call XInitThreads very very early on, ie.
> before touching anything X, even it it didn't need any threading
> support.
> 

	Yes, you need to call XInitThreads() BEFORE XOpenDisplay().

Cheers.