https://bugs.kde.org/show_bug.cgi?id=444535

            Bug ID: 444535
           Summary: Window filtering conditions for custom shortcuts
                    (usually) don't work
           Product: systemsettings
           Version: 5.23.2
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: kcm_khotkeys
          Assignee: k...@michael-jansen.biz
          Reporter: adam.m.fontenot+...@gmail.com
                CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
This is potentially annoying to debug because it seems to rarely function just
fine. It's just that usually, it doesn't. I'm happy to follow any debugging
suggestions given, I can even recompile khotkeys if necessary.

STEPS TO REPRODUCE
1. Create a new custom shortcuts group.
2. Set the action to be anything involving an active window. I set mine so that
the window title has to contain "a".
3. Add a global shortcut that sends keyboard input to the group. Set the
trigger to whatever you like, and the action to insert some arbitrary text.
4. Click in a window that matches the requirements you set in 2.

OBSERVED RESULT
The window behaves as if there was no shortcut. If I set the shortcut to Alt+O,
for example, then "o" is printed in the textbox that has focus. If the program
that owns the window has its own shortcuts, those execute instead of the global
shortcut.

EXPECTED RESULT
The window does not receive the key events at all. Instead, whatever text was
entered in step 3 is typed into the window instead.

SOFTWARE/OS VERSIONS
Linux: Arch Linux x86_64 (kernel 5.14.14)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

OTHER NOTES:
Certain shortcuts triggers disappear when I close and reopen system settings. I
assume that issue is https://bugs.kde.org/show_bug.cgi?id=300532 There seems no
pattern to which shortcuts don't work - none of them, to my knowledge, is
otherwise bound as a global shortcut.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to