diff options
| author | Owen W. Taylor <otaylor@fishsoup.net> | 2014-05-09 18:21:05 -0400 |
|---|---|---|
| committer | Ulrich Sibiller <uli42@gmx.de> | 2016-10-19 21:40:29 +0200 |
| commit | afc7138f952ff28a27a43452d6ea8e1ae82ae8cd (patch) | |
| tree | ab0f9c208c2dbb3453e094a31dbbb1dec6b326f3 /debian/README.source | |
| parent | 88d496598fbf36724c1a825875a4becdfc29d600 (diff) | |
| download | nx-libs-afc7138f952ff28a27a43452d6ea8e1ae82ae8cd.tar.gz nx-libs-afc7138f952ff28a27a43452d6ea8e1ae82ae8cd.tar.bz2 nx-libs-afc7138f952ff28a27a43452d6ea8e1ae82ae8cd.zip | |
Fix XNextRequest() after direct usage of XCB
When XCB owns the X socket, dpy->request is not updated, so
NextRequest() and XNextRequest() return the wrong value. There's
nothing we can do to fix NextRequest() while retaining ABI compat,
but change XNextRequest() to grab the socket back from XCB,
updating dpy->request.
Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
Reviewed-by: Uli Schlachter <psychon@znc.in>
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Backported-to-NX-by: Ulrich Sibiller <uli42@gmx.de>:
Added #ifdefs to be aware of changes regarding XCB in case we later
switch to XCB.
Diffstat (limited to 'debian/README.source')
0 files changed, 0 insertions, 0 deletions