https://bugs.kde.org/show_bug.cgi?id=383052
--- Comment #6 from Alain Knaff <[email protected]> --- Indeed, it seems to be XGrabKeyboard that they are doing, thanks for the pointer. The workaround at https://bugs.freedesktop.org/show_bug.cgi?id=21652#c4 succeeds in addressing the issue, without any negative side-effects. I'm just wondering why such disruptive functions still exist in the X API :-( -- You are receiving this mail because: You are watching all bug changes.
