This bug report was migrated from our old Bugzilla tracker.

Reported in version: 2.0.0
Reported for operating system, platform: Linux, x86_64

Comments on the original bug report:

On 2013-10-07 22:14:02 +0000, wrote:

Forwarding bug report to Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725265

---

From: Darren Salt bugspam@moreofthesa.me.uk
Subject: SDL 2: interaction with window managers and edge workspace flipping
Date: Thu, 03 Oct 2013 14:11:30 +0100
Package: libsdl2-2.0-0
Version: 2.0.0+dfsg1-1

I've noticed that, with at least two window managers and an SDL-managed
window which extends to the edges of one monitor and has mouse grab, there is
a problem with edge-based workspace flipping due to the WM having created
windows around the edges of the display.

What happens is that the app (game, whatever; I'm using Unvanquished ‘sdl2’
branch for this) receives a LeaveNotify event then no button press events
(though mouse motion events still happen) until the pointer leaves the WM's
edge window (such that the game receives an EnterNotify event), at which
point button events may be received again. Result is lost button events so
far as the game is concerned.

I have not observed this problem with SDL 1.2, most likely due to it
resetting the pointer position sufficiently often.

[Unvanquished source: https://github.com/Unvanquished/Unvanquished]

On 2018-08-06 21:20:21 +0000, Ryan C. Gordon wrote:

Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.