[pygtk] Xlib: unexpected async reply (sequence 0x10e6b)!

[Nikos Kouremenos]

On Thu, 31 Mar 2005 14:47:22 +0300, Nikos Kouremenos <kourem at gmail.com> wrote:
> On Thu, 31 Mar 2005 13:37:06 +0200, Antoon Pardon
> <Antoon.Pardon at rece.vub.ac.be> wrote:
> >
> > That is the error I get.
> >
> > First some background.
> >
> > http://www.pygtk.org/pygtk2reference/gdk-functions.html 
> >
> > In the entry gtk.gdk.threads_init I read the following:
> >
> > | PyGTK does not release the GIL when calling a GTK or GDK function.
> > | Also it does not acquire the GDK global lock (GGL). This means that,
> > | in effect, Python threads can use the GIL alone to serialize access to
> > | the GTK and GDK libraries. Of course, if there are non-Python threads
> > | calling GTK or GDK functions the GGL must be used.
> >
> > However when I remove the gtk.threads_leave() and gtk.threads_enter()
> > calls from my program after sometime the program crashes and I get the
> > following message:
> >
> >   Xlib: unexpected async reply (sequence 0x10e6b)!
> >
> > Now I'm wondering. Is this a bug in pygtk or is the documentation not
> > accurate? I'm using python 2.3.5 and pygtk 2.6.1 on a Debian testing
> > machine.
> 
> Threads can be  a pain in the ass. If you handling gui then you should
> not remove threads_enter()/leave(). If you're not doing gtk stuff and
> you still get this problem then I cannot help :)

Ok if that the above text in reference different then I'm ok.
I just resend to say that I have seen problem countless times and have
seen it even with latest Bittorent GUI 2 times {then switched to
curses which rock}] I hope the were right switching to GTK from
wxWidgets..

-- 
Nikos Kouremenos | Jabber ID: nkour at jabber.org | http://members.hellug.gr/nkour