<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Intel DRI 2 can't grab the server within Dota 2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102277">102277</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Intel DRI 2 can't grab the server within Dota 2
</td>
</tr>
<tr>
<th>Product</th>
<td>xorg
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver/intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>chris@chris-wilson.co.uk
</td>
</tr>
<tr>
<th>Reporter</th>
<td>tod.jackson@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>"Alt-tabbing" does not work properly within Dota 2. I had previously thought
this was a Ratpoison WM specific issue, but then I tested CWM and it exists
also.
You basically cannot switch windows when xf86-vide-intel + DRI 2 and Dota 2 are
running. Under Ratpoison it seems like there are issues grabbing the server
(the "expectant" cursor appears under Ratpoison but then the screen just
flickers. If you do manage to tab out, with persistence, once you tab in the
screen continues to flicker as if it's waiting to be focused.
Seems to be a non-issue on DRI 3 and modesetting, however those are a
non-solution without TearFree. TearFree is seriously mandatory on IvyBridge. :)
Tested xf86-video-intel at commit 2100efa105e8c9615eda867d39471d78e500b1bb and
most up-to-date Ratpoison with and without an EWMH hack, as well as CWM 5.6.4.
This is actually about a year long issue so I'm very surprised it never got
supported. That goes to myself as well. ;/</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>