<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - BadAccess errors in ShmAttach due to thread races with XNextRequest() usage in cairo-xlib-surface-shm.c"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98883#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - BadAccess errors in ShmAttach due to thread races with XNextRequest() usage in cairo-xlib-surface-shm.c"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98883">bug 98883</a>
from <span class="vcard"><a class="email" href="mailto:bugs.freedesktop@karlt.net" title="Karl Tomlinson <bugs.freedesktop@karlt.net>"> <span class="fn">Karl Tomlinson</span></a>
</span></b>
<pre>(In reply to Daniel van Vugt from <a href="show_bug.cgi?id=98883#c14">comment #14</a>)
<span class="quote">> The patch says:
>
> "XShmAttach returns True, even on error."
>
> and
>
> "XShmAttach is hard-coded in libXext to return True, even on failure."</span >
The question was what error or failure, and why is that happening.
XShmAttach returns True to indicate it successfully queued the request.
It does not fail to queue the request.
If the server fails to process the request successfully, then it sends an
error response.
It would be helpful to understand why you are expecting an error response.
The best clue appears to be the patch at the end of
<a href="https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056">https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>