X display locking

2013-03-07 Thread Torsten Jager
Hello! What is the proper usage of XLockDisplay () / XUnlockDisplay () when an application has multiple threads using * "normal" Xlib functions * Xitk functions * libGL and/or * libvdpau ? On my machine (libX11 1.4.0) bracketing all 4 seems to be necessary to avoid lockups and stack corr

Re: X display locking

2013-03-07 Thread Alan Coopersmith
On 03/ 7/13 06:31 AM, Torsten Jager wrote: > What is the proper usage of XLockDisplay () / XUnlockDisplay () > when an application has multiple threads using Applications should never call those functions - they are Xlib's internal locking mechanism for the request buffers. Applications should on

Re: X display locking

2013-03-07 Thread Aaron Plattner
On 03/07/2013 06:31 AM, Torsten Jager wrote: Hello! What is the proper usage of XLockDisplay () / XUnlockDisplay () when an application has multiple threads using * "normal" Xlib functions * Xitk functions * libGL and/or * libvdpau ? XLockDisplay / XUnlockDisplay is only required

[ANNOUNCE] xorg-server 1.13.3

2013-03-07 Thread Matt Dew
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Airlie (1): randr: cleanup provider properly Matt Dew (1): Bump version to 1.13.3 git tag: xorg-server-1.13.3 http://xorg.freedesktop.org/archive/individual/xserver/xorg-server-1.13.3.tar.bz2 MD5: 63c2530476cba4f0283570bbb650