We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3329

Summary: Some games have issues with Xmonad
Product: SDL Reporter: killian.de.volder
Component: videoAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2    
Version: don't know   
Hardware: x86_64   
OS: Linux   
URL: https://github.com/ValveSoftware/Dota-2/issues/359

Description killian.de.volder 2016-05-10 15:43:36 UTC 
If one launches the game, it first shows a logo/loading screen. After it's loaded you get a black screen a working mouse cursor.
It's as if the game no-longer sends SDL updates.

Game works on fluxbox for example.
Comment 1 killian.de.volder 2016-05-11 08:45:22 UTC 
Works when launched with -fullscreen.
Not sure if the game can be blamed, or if it's sdl's fault.
Strictly speaking I suspect the blame is either xmonad sending proper updates, or SDL getting confused by the (out-side-the-norm) signals xmonad sends.

It might also fail in herbstluftwm according to this other bugs:
https://github.com/ValveSoftware/Dota-2/issues/359
The patch notes don't seem to mention any technical changes though :/
Comment 2 Ryan C. Gordon 2018-08-06 21:20:22 UTC 
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.