Bug 345542

Summary:	Ambiguous Shortcuts For Any Action
Product:	[Applications] kate	Reporter:	Max Schaefer <max>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	kare.sars, ndesmoul, pfoo, pietz, simon.persson
Priority:	NOR
Version:	5.0.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot

Description Max Schaefer 2015-03-26 11:39:07 UTC

Any shortcut I use in Kate gives me this error (SHORTCUT HERE was inserted by myself):

The key sequence 'SHORTCUT HERE' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.

Reproducible: Always

Steps to Reproduce:
1. Open Kate
2. Attempt to use a shortcut (Ctrl+C, Ctrl+S, etc)

Actual Results:  
The key sequence 'Ctrl+S' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.

Expected Results:  
Shortcut actions occurring as normal.

I am on latest Arch Linux official packages as of the 26th of March 2015.
I have reset shortcuts in both Kate and the Application Keyboard Shortcuts in System Settings.

Comment 1 Max Schaefer 2015-03-26 11:45:29 UTC

Created attachment 91754 [details]
Screenshot

Comment 2 ndesmoul 2015-05-05 11:42:36 UTC

Hello,

I confirm this bug (with plasma 5.3). I'm also using Archlinux.
It is not limited to Kate though as similar problems occur  with gwenview.

Comment 3 ndesmoul 2015-05-07 12:27:01 UTC

This bug seems to be the same as Bug 343665: https://bugs.kde.org/show_bug.cgi?id=343665

Comment 4 pietz 2015-07-22 23:48:52 UTC

I also can confirm this. Please fix this fast! I am wondering why none of the developers uses shortcuts in kate and gets an error message... What editor do you use? Maybe I should switch, too :-)

Comment 5 Kåre Särs 2015-07-23 06:09:25 UTC

This is probably a distro dependent thing as the shortcuts work OK on Kubuntu...

Comment 6 Simon Persson 2015-09-01 03:08:29 UTC


*** This bug has been marked as a duplicate of bug 343665 ***