<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - ThinkPad T450: RetroArch refuses to go back into windowed mode after fullscreen" href="https://bugs.freedesktop.org/show_bug.cgi?id=96767#c38">Comment # 38</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - ThinkPad T450: RetroArch refuses to go back into windowed mode after fullscreen" href="https://bugs.freedesktop.org/show_bug.cgi?id=96767">bug 96767</a> from <a class="email" href="mailto:diego.viola@gmail.com" title="Diego Viola <diego.viola@gmail.com>"> Diego Viola</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=96767#c37">comment #37</a>) > (In reply to Diego Viola from <a href="show_bug.cgi?id=96767#c34">comment #34</a>) > > Is this patch no longer relevant for this problem? > > > > <a href="https://bugs.freedesktop.org/attachment.cgi?id=121524">https://bugs.freedesktop.org/attachment.cgi?id=121524</a> > > We fixed that bug in Xorg. > > commit e43abdce964f5ed9689cf908af8c305b39a5dd36 > Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> > Date: Wed Feb 3 09:54:46 2016 +0000 > > dri2: Unblock Clients on Drawable release > > If the Window is destroyed by another client, such as the window > manager, the original client may be blocked by DRI2 awaiting a vblank > event. When this happens, DRI2DrawableGone forgets to unblock that > client and so the wait never completes. > > Note Present/xshmfence is also suspectible to this race. > > Testcase: dri2-race/manager > Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> > Cc: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>> > Reviewed-by: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>> Yes, I remember now. I still think xf86-video-intel+sna+dri2 shouldn't give different results than modesetting+glamor+dri2 for this use case, although I still get this bug even with Linux 4.8.1 and I've been bisecting from Linux 4.0 and up. That said, I realize you are busy and I'd hate to distract you with this. This seems like the last bug that I know of when it comes to RetroArch on Intel and I'd love for this to be fixed. Thanks for all of your help so far.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>