Your message dated Mon, 27 Apr 2020 10:06:40 +0100
with message-id <[email protected]>
and subject line Re: Bug#902472: sdl2: can deadlock after hiding a window
has caused the Debian Bug report #902472,
regarding sdl2: can deadlock after hiding a window
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
902472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902472
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libsdl2
Version: 2.0.5+dfsg1-3
Tags: stretch patch

It can happen that SDL gets stuck waiting for X to accept a grab request, when 
the
window has already been hidden with SDL_HideWindow.

This behaviour has been fixed in 2.0.6 with commit 8f0a002 "x11: Don't loop 
forever
if the X server refuses a pointer grab", and does fix the problem for me when 
cherry-picking
that commit.

It would be great if that patch could find its way in a stretch update.  In any 
case since
it would take some time to get the fix to users, it would be good to get a 
backport to point
impacted users to.  Would you mind if I uploaded a 2.0.8 backport ?

--- End Message ---
--- Begin Message ---
Version: 2.0.6+dfsg1-1

On Sun, 30 Sep 2018 at 18:17:37 +0100, Simon McVittie wrote:
> On Wed, 27 Jun 2018 at 01:28:42 +0200, [email protected] wrote:
> > This behaviour has been fixed in 2.0.6
> 
> Closing the bug as fixed in testing/unstable. It remains valid for
> stretch, but BTS version tracking will keep track of that.

Really closing the bug now...

On Wed, 27 Jun 2018 at 01:28:42 +0200, [email protected] wrote:
> It would be great if that patch could find its way in a stretch update.

stretch is now oldstable, and this is fixed in buster, so it's unlikely
that this will happen. Upgrading to buster is recommended.

    smcv

--- End Message ---

Reply via email to