Bug 444176

Summary: Key strokes are propagated to window contents while resizing/moving window by keyboard only
Product: [Plasma] kwin Reporter: Nico Dorn <nicodorn>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: CONFIRMED ---    
Severity: normal CC: john.kde, lukasz.wojnilowicz, n.parkanyi, nate, sephiroth_pk
Priority: NOR    
Version First Reported In: 5.23.1   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: X11Client patch

Description Nico Dorn 2021-10-21 08:54:42 UTC 
SUMMARY
If one tries to resize/move a window only by using the keyboard, the key strokes are propagated to the active application which runs inside the window. This is a longstanding bug (several years old).

STEPS TO REPRODUCE
1. Open Konsole.
2. Move the window only using the keyboard: Alt + F3 > More Actions > Move > Cursor keys up/down/right/left > Enter when satisfied.

OBSERVED RESULT
If you hit the up or down cursor during the moving process Konsole's history function is invoked. The Enter key to complete the action produces an new blank prompt or executes the command on the prompt.

EXPECTED RESULT
Key strokes should not be propgated to the application during moving action.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-38-generic (64-bit)
Graphics Platform: X11
Comment 1 n.parkanyi 2021-10-27 06:44:01 UTC 
I stumbled upon this recently as well, it only happens in X11.
Changing X11Client to always grab the keyboard during resize/move
(see attached diff), fixes this...but with the undesirable side effect
that Qt widgets appear "unfocused" whenever you move/resize a window.
Comment 2 n.parkanyi 2021-10-27 06:44:46 UTC 
Created attachment 142932 [details]
X11Client patch
Comment 3 Vlad Zahorodnii 2021-10-27 07:18:51 UTC 
see also https://invent.kde.org/plasma/kwin/-/merge_requests/90
Comment 4 Vlad Zahorodnii 2023-02-07 08:51:15 UTC 
*** Bug 465390 has been marked as a duplicate of this bug. ***
Comment 5 John Veness 2025-04-28 20:03:11 UTC 
*** Bug 479077 has been marked as a duplicate of this bug. ***