deadlock on some X environments (was: reading relay log)

Ferenc Wagner wferi at
Thu Jan 8 14:27:16 CST 2004

Ferenc Wagner <wferi at> writes:

> For me it seems XCreateDC does not return (the one I quoted
> from the Wine source).  I mean, sometimes.  Because the same
> program works now...  I did not even recompile it, honest.
> I am going mad.  Yesterday night it was 100% reproducible.

Making progress.  The thing does not depend on time or
weather, but instead on the terminal I'm using.  Different X
extensions, color depth, whatever.  On --debugmsg +all logs

$ diff -u run_head.log lock_async.log
+0009:trace:opengl:X11DRV_OpenGL_Init GLX is up and running error_base = 77
-0009:trace:x11settings:X11DRV_Settings_AddOneMode initialized mode 0: 1024x768x16 @0 Hz (NoRes)
+0009:trace:x11settings:X11DRV_Settings_AddOneMode initialized mode 0: 1024x768x32 @0 Hz (NoRes)
+0009:trace:xrender:X11DRV_XRender_Init Xrender is up and running error_base = 179
-0009:trace:xrender:X11DRV_XRender_Init Xrender is not available on your XServer, client side rendering with the core protocol instead.
-0009:Ret  x11drv.GetDeviceCaps() retval=00000010 ret=40899a22
+0009:Ret  x11drv.GetDeviceCaps() retval=00000018 ret=40899a22
-0009:trace:x11drv:X11DRV_CreateBitmap (0x68) 36x18 16 bpp
+0009:trace:x11drv:X11DRV_CreateBitmap (0x68) 36x18 24 bpp

Does it ring the bell for anybody?  It's getting far too
deep for me...  The whole logs are available at{run_head,lock_async}.log


More information about the wine-devel mailing list