Bug 466014

Created attachment 156447 [details]
KWin Popup Notification

CAVEAT
***
I have never filed a bug report.  The best place I could discern to report this is Kwin.  I see that in the past bugs have neen reported in Product: SystemSettings (e.g #458795), but I could not find SystemSettings as a listed product.  This may not be a Kwin problem because it's related to "Common Actions" and not KWin specific shortcuts.  If it needs to be moved, please do so.
***

SUMMARY SHORT
***
After changing shortcuts, when I try to use them I receive a "The key sequence 'Ctrl+E' (e.g)  is ambiguous. Use 'Configure Keyboard Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered" message."
***

SUMMARY LONGER
***
I am specifically trying to create Emacs navigation and edit bindings globally.  I want Ctrl+a to go to the beginning of a line, Ctrl+f to advance one character/space forward, Ctrl+d to delete under point, etc., basically the usual defaults of Bash/Emacs/Jmacs.  After I set and apply them, when I try to use them in, say in KWrite, Ctrl+a (beginning of line) and Ctrl+x,h (select all) work as expected but many other give me the ambiguity error above, or do nothing.  A Iong time ago I settled on Debian and KDE/Plasma, I would prefer a native solution without resorting to tools like AutoKey, XBindKeys, or other applications.
***

STEPS TAKEN
***
I have unticked every default "Custom Shortcut" because I don't use them.  I have made sure that under Input|Keyboard|Advanced that nothing else is ticked except for my swapping of CONTROL-L and CAPSLOCK.  I have gone through individually each shortcut and looked for anything using Ctrl+e (e.g), and searched as well and nothing else is using any of the ones that give me the ambiguity error. I have unticked or deleted every default that uses a particular shortcut (e.g. Edit|TextCompletion).  I have also chosen yes each time the system told me that the shortcut I wanted was already in use (e.g. Ctrl+a for "select all") and did I want to replace it.

I have searched the Web, forums, and Bug Tracker.  I have only found very old discussions (like https://forum.kde.org/viewtopic.php?t=151953).  Searching the Bug Tracker for "shortcuts" and "ambiguity" doesn't return relevant results.  If I missed an opened or closed report please accept my apologies and direct me to it.
***

STEPS TO REPRODUCE
1.  Open SystemSettings|WorkSpace|Shortcuts|Shortcuts and scroll down to Common Actions
2.  Pick a shortcut you wish to change. I recommend changing "End of Line" because I know that is one.  Change the input to Ctrl+e.  If it says it's in use and asks if you want to replace it pick yes. It also happens with ctrl+b as "back one character/space".  With Ctrl+f as forward a character/space, nothing happens at all (in KWrite) but the right arrow key still advances the caret even though I have unticked both "Forward" and "Alt+Right" as defaults.  I have also searched Shortcuts for "Right" and found nothing ticked. However, Alt-f will advance a word.
3. Apply
4. Open an application where that shortcut is useful (Kate, Kwrite, etc).

OBSERVED RESULT
Several described in 2 above.  Another observed result is that in this field using Firefox Ctrl+a still selects all.  It does not go to the beginning of the line like it does in KWrite.  Further, whereas Ctrl=b gives me the ambiguity error in KWite it still opens Bookmarks in Firefox, and ctrl+f opens the find dialogue even though I have the Plasma Intergration extension active.


EXPECTED RESULT
For my chosen shortcuts to work globally in Plasma using any Common Action shortcut.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kernel 6.0.0-1
(available in About System)
KDE Plasma Version:  5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Graphics Platform: X11

ADDITIONAL INFORMATION
I am not sure this is a bug.  I am just a user.  I selected minor, but maybe everything is working exactly as expected by the Amazing Developers of KDE (tm).  In that case it should be refiled under "wishlist," and I will seek non-native solutions.  Thanks for all your fantastic work! I especially apologize to whomever has to read this is if it's not actually a bug or if I filed it poorly or in the wrong place.