<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Compiz freezes when undocking Lenovo T450s, hang in xcb_wait_for_reply/wait_for_reply/_xcb_conn_wait"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94461#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Compiz freezes when undocking Lenovo T450s, hang in xcb_wait_for_reply/wait_for_reply/_xcb_conn_wait"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94461">bug 94461</a>
from <span class="vcard"><a class="email" href="mailto:cs_gon@yahoo.com" title="cs_gon@yahoo.com">cs_gon@yahoo.com</a>
</span></b>
<pre>Some additional information:
I'm not sure if this is a libxcb bug, but I found some older bugs with pretty
much the same symptoms and call traces. This is the reason I reported it here.
If this is not a libxcb bug, hopefully you can point me in the right direction.
The problem started to appear after updating to the Wily HWE stack (with kernel
4.2). I cannot reproduce the problem with older kernels (e.g. 3.16 or 3.18),
but with any newer kernel, up to the latest 4.5 versions (including drm-next
and drm-intel-nightly branches).
As far I can see, compiz only uses one thread to do X calls. Especially for the
stack trace I attached, no other compiz threads were in any X calls.
Compiz does not call XInitThreads(), but I added the call before any other X
calls, just in case. But then compiz does not fully start (shows the Unity
panels, but does not draw a background), and then hangs in a XLockDisplay()
call. And just like before, the other threads are not in any X calls. So IMHO
that does seem point in the direction of libxcb!?
If you need any more information, please let me know. Thanks!</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>