https://bugs.kde.org/show_bug.cgi?id=383052
--- Comment #8 from Alain Knaff ---
>> I'm just wondering why such disruptive functions still exist in the X API :-(
>
> Because you cannot break it.
But *why* can't you remove it? Even screensavers don't depend on this nowadays
(just tried it. Start s
https://bugs.kde.org/show_bug.cgi?id=383052
Martin Flöser changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=383052
--- Comment #6 from Alain Knaff ---
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-ef
https://bugs.kde.org/show_bug.cgi?id=383052
Alain Knaff changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://bugs.kde.org/show_bug.cgi?id=383052
Martin Flöser changed:
What|Removed |Added
Component|libinput|general
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=383052
--- Comment #3 from Alain Knaff ---
52.2.0 (64-bit)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383052
Martin Flöser changed:
What|Removed |Added
Severity|critical|normal
--- Comment #2 from Martin Flöser ---
R
https://bugs.kde.org/show_bug.cgi?id=383052
Martin Flöser changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Resolution|---
