https://bugs.kde.org/show_bug.cgi?id=359157
--- Comment #11 from Thomas Lübking <thomas.luebk...@gmail.com> --- Nope, it's (most likely just) focus stealing prevention. The dialog has no WM_CLASS nor any other relation to it's main window (the game) So not only is it NOT a transient (ie. marked to always stay above the game what's likely desired) nor can kwin determine that it's a related window. So it denies activation (and raising) This patch may resolve this (at least let it raise above) https://git.reviewboard.kde.org/r/124130/ The actual problem though is the complete lack of hints on the dialog, notably not being a transient as could be expected. You can confirm the above by setting the focus stealing prevention to "none" in "kcmshell5 kwinoptions", first tab. That however doesn't explain the inability to successfully focus the dialog. It neither provides WM_HINTS, but should be considered to take focus by default. What's suspicious is that the game window denies focus resp. relies on the wonky WM_TAKE_FOCUS protocol (*sigh*, I thought Java was the last remainder) to handle the focus assignment itself. => Can you activate any (other) window when alt+tabbing away from the game window and if so, what happens when you try to alt+tab to the dialog (not! the game) from that 3rd (eg. kwrite or dolphin) window? -- You are receiving this mail because: You are watching all bug changes.
