URL:
<http://savannah.gnu.org/bugs/?29539>
Summary: XNEE related XLIB problem has been fixed
Project: Xnee
Submitted by: rjy
Submitted on: Tue 13 Apr 2010 10:48:02 AM GMT
Category: libxnee
Severity: 3 - Normal
Item Group: Minor fault
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
Hi,
A while back there were problems with multiple display connections in XNEE.
Originally it was thought that it had something to do with broken record
implementation in X server. It turns out that it was caused by a general
synchronization problem in Xlib configured using --with-xcb option.
Reported bug: https://bugs.freedesktop.org/show_bug.cgi?id=27595
Patch:
http://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=75ea8c37935ccc911557d16a303ba595b8ab106b
When the fixed Xlib is taken into use in distributions you can fix XNEE to
start using separate connections again:
if ( xnee_record_from_data_display(xd))
{
/*
* From X.org 1.6.0 to ????
*
* there seem to be something strange about
* the XRecordCreateContext call
* which causes the XRecordEnableContextAsync
* to fail ... ugly fix, but it works
*
*/
fprintf(stderr, "Workaround: Creating context on data display instead
of control \n");
fprintf(stderr, " You can ignore this message\n");
context_display = xd->data ;
}
-- Rami
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?29539>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-xnee mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-xnee
