Yeah I believe you're right. I definitely have this in my environment. And when I run with `MOZ_USE_XINPUT2=0` then the bug doesn't appear anymore. Somewhat confusingly I initially ran with `MOZ_USE_XINPUT2=` (with no value), which (I think) should have also reset the option, but according to [the code](https://searchfox.org/mozilla-central/rev/a156a65ced2dae5913ae35a68e9445b8ee7ca457/toolkit/xre/nsAppRunner.cpp#4786) this doesn't also sets the value just like using `1`. (in these tries I always had `MOZ_ENABLE_WAYLAND=` too, to make sure that I was using xwayland).
Bug 1805703 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Yeah I believe you're right. I definitely have this in my environment. And when I run with `MOZ_USE_XINPUT2=0` then the bug doesn't appear anymore. Somewhat confusingly I initially ran with `MOZ_USE_XINPUT2=` (with no value), which (I think) should have also reset the option, but according to [the code](https://searchfox.org/mozilla-central/rev/a156a65ced2dae5913ae35a68e9445b8ee7ca457/toolkit/xre/nsAppRunner.cpp#4786) this does also set the value just like using `1`. (in these tries I always had `MOZ_ENABLE_WAYLAND=` too, to make sure that I was using xwayland).