[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 --- Comment #7 from David Edmundson --- Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 --- Comment #6 from Geoffrey McRae --- Confirmed still bugged on 5.27.7. Minimum viable sample still reproduces the issue. Application incorrectly looses focus when `XKeyboardUngrab` is called. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 Geoffrey McRae changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|UNMAINTAINED|--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 --- Comment #5 from Geoffrey McRae --- Or, you could use the minimal code I produced and check if it's still an issue instead of just flat out closing an issue that is years old because of your inaction. When this was opened it was the most current version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #4 from David Edmundson --- This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 --- Comment #3 from Geoffrey McRae --- Sorry I misread what you stated. The problem is when the application calls XKeyboardUngrab, which sends the FocusOut event with NotifyUngrab as far as I am aware. Either way, the sample application provided reliably replicates the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 --- Comment #2 from Geoffrey McRae --- As per: https://tronche.com/gui/x/xlib/input/XUngrabKeyboard.html > The XUngrabKeyboard() function releases the keyboard and any queued events if > this client has it actively grabbed from either XGrabKeyboard() or > XGrabKey(). XUngrabKeyboard() does not release the keyboard and any queued > events if the specified time is earlier than the last-keyboard-grab time or > is later than the current X server time. It also generates FocusIn and > FocusOut events. The X server automatically performs an UngrabKeyboard > request if the event window for an active keyboard grab becomes not viewable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431133] XKeyboardUngrab generated FocusOut event improperly handled
https://bugs.kde.org/show_bug.cgi?id=431133 --- Comment #1 from Vlad Zahorodnii --- > `FocusOut` event is generated with the mode set to `NotifyUngrab` Shouldn't it be NotifyGrab? -- You are receiving this mail because: You are watching all bug changes.
