I tried this game: https://store.steampowered.com/app/2290/Final_DOOM/ which is a DOSBOX game running trough proton (wine packaged by steam). I'm using a steam flatpak. The above shouldn't be relevant, though. The game doesn't work (black screen), I can't alt-tab out, as it comes back on top. When starting it, I get a message about pointer confinement. When closing the game trough alt-f4, my cursor remains locked in place, and I have to alt-tab once more, or press escape for seconds to unlock it. Pointer confinement should be released when the window that asked it is closed. There is also a minor alt-tab issue here, not sure if I should report it, as I don't have much information.
Related closed bugs https://bugs.kde.org/show_bug.cgi?id=395815 https://bugs.kde.org/show_bug.cgi?id=388885 How did you launched Final DOOM in Linux? - says invalid platform for me and no install/play button
(In reply to Alexander Mentyu from comment #1) > Related closed bugs https://bugs.kde.org/show_bug.cgi?id=395815 > https://bugs.kde.org/show_bug.cgi?id=388885 > > How did you launched Final DOOM in Linux? - says invalid platform for me and > no install/play button I played it (tried to) trough SteamPlay, though you need to enable it for every game in your library. Steam settings -> steamplay -> Enable for all titles. Try not to spend too much time playing around with this ;-) I put a screenshot of the setting there some time ago: https://askubuntu.com/a/1067783/483325 Note that it isn't specific to that game (I tested this one because I needed something light), I remember seeing something similar after playing VVVVVV, which was also grabbing the mouse for some reason. The issue here is really to release the pointer after a game quit, if it didn't do it itself. This indeed seems like a duplicate of Bug 388885, which I didn't see while searching. Looks like the fix will only land in the next plasma release (fix landed in git the 26th of june, 5.13 was released on the 12th). Thanks for pointing this out. *** This bug has been marked as a duplicate of bug 388885 ***