https://bugs.kde.org/show_bug.cgi?id=506141
--- Comment #1 from Ming Chuan <m...@culpring.com> --- I added logging to https://github.com/qt/qtwayland/blob/6.9.0/src/client/qwaylandinputdevice.cpp , together with `WAYLAND_DEBUG=1` to observe the timestamp of wayland event processing, here is what's happening 1. User press ctrl+g on their keyboard 2. Wayland compositor send `wl_keyboard` key press event to krita 3. krita enters a busy state (probably busy calculating new group layer thumbnail?), stops reading any new wayland event 4. User releases ctrl+g key on their keyboard 5. The key repeat timer in `QWaylandInputDevice::Keyboard::Keyboard` got fired while krita is busy, a key repeat event is generated 6. krita leaves busy state, starts reading wayland events again, receives key release event and cancel the key repeat timer, but it's too late as the repeat event has been passed to application code for handling 7. qt.gui.shortcutmap groups the layer twice When I repro this, krita stayed in "busy state" for about 950ms -- You are receiving this mail because: You are watching all bug changes.
