https://bugs.kde.org/show_bug.cgi?id=490985
--- Comment #3 from Timo Gurr <timo.g...@gmail.com> --- (In reply to Nate Graham from comment #1) > What does Meta+F2 do on your system? krunner. Afaik ALT+F2 is the standard for krunner these days. It's also reproducible after reverting to the standard ALT+F2 among other like ALT+SPACE. It also affects any other shotcuts. (In reply to fanzhuyifan from comment #2) > Fwiw I cannot reproduce the bug on X11, git build, if I assign Meta+F2 to > launch dolphin. Keyboard input still works after triggering that shortcut. > Also the referenced commit doesn't change the keyboard grabbing logic for > ordinary (not modifier-only) shortcuts, so something else seems be causing > the issue here. > > Is this problem reproducible for a new user? If not figuring out the minimal > config that can cause this issue would be useful. It's not restricted to Meta+F2 but any other shortcut, e.g. every time globalacceld seems to come into play. It's also reproducible on a completely new user without any pre-existing configs. I've recorded a video also capturing keypresses, once the curser in the konsole windows changes from the filled white rectangle to the rectangle with just the white border e.g. window loosing focus thats the moment where I tried to launch e.g. krunner with ALT+F2. When the screen goes black I switched tty to be able restart the plasma-kglobalaccel user-service, which is the konsole window to the right where I share a screen session so you can see everything what I did. After restarting the service you can see the typed letters appearing in the konsole window I was typing to. Video: https://nextcloud.deltaquadrant.org/s/mA9wPRMAwXkHQJJ/download/kglobalacceld.mp4 -- You are receiving this mail because: You are watching all bug changes.
