From 3aeeb53d737798923b73bc99d43c0e84cf28eebe Mon Sep 17 00:00:00 2001 From: =?utf8?q?Samuel=20R=C3=B8dal?= Date: Tue, 29 Nov 2011 10:16:57 +0100 Subject: [PATCH] Prevented Xlib sequence errors in xcb plugin. Prevent Xlib errors of the form "Xlib: sequence lost (0x2716a > 0x1717c) in reply type 0x11!" from being printed. We know the cause of these is because we're manually calling the XESetWireToEvent handlers since those are not handled by XCB, and this confuses Xlib since it's then seeing events with old sequence numbers. We simply set the sequence number to the latest sequence number and the errors go away. Change-Id: I2a9e7a7cfd0ba8692e43ce61f796a8189305e0d3 Reviewed-by: Simon Hausmann Reviewed-by: Jocelyn Turcotte --- src/plugins/platforms/xcb/qxcbconnection.cpp | 1 + 1 file changed, 1 insertion(+) diff --git a/src/plugins/platforms/xcb/qxcbconnection.cpp b/src/plugins/platforms/xcb/qxcbconnection.cpp index 15f6904..a5b8aa9 100644 --- a/src/plugins/platforms/xcb/qxcbconnection.cpp +++ b/src/plugins/platforms/xcb/qxcbconnection.cpp @@ -566,6 +566,7 @@ void QXcbConnection::handleXcbEvent(xcb_generic_event_t *event) if (proc) { XESetWireToEvent((Display*)m_xlib_display, response_type, proc); XEvent dummy; + event->sequence = LastKnownRequestProcessed(m_xlib_display); proc((Display*)m_xlib_display, &dummy, (xEvent*)event); } } -- 2.7.4