Bug 236480

Summary:	ambiguous shortcuts
Product:	[Applications] kate	Reporter:	criptych
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	rob
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description criptych 2010-05-05 21:57:52 UTC

Version:           3.4.2 (using 4.4.2 (KDE 4.4.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.32-21-generic

After upgrading from 'karmic' to 'lucid' LTS, Kate does not allow using Ctrl+F or F3 shortcuts (and possibly others), giving the message: "The key sequence 'Ctrl+F' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered."
However, after ensuring that the shortcuts are unique and even resetting all to defaults, the same message still appears.

Comment 1 Dominik Haumann 2010-05-09 05:05:21 UTC

which plugins are visible in the toolviews?

Comment 2 rob 2010-06-20 11:00:57 UTC

I have same problem with Kate on lucid using the CTRL+f/c/v shortcuts. However, it is very intermittent. Often closing/reopening/clicking around in Kate seems to fix it. 

I have two tools/plugins enabled in Configure>Application>Plugins: "Kate Python Browser Plugin" and "Find in files tool view". 

Just now after disabling the python browser (no restart) the shortcut issue went away. However then reenabling the python browser (again no restart) and the problem didnt return. After a restart, the ambiguous shortcut has returned again, this time all i did was click on the second view (two vertical split views) and this was enough to fix. Not sure if it has anything to do with the python plugin.

Hope thats indicative. Let me know if there's any other debugging info i can collect.

Comment 3 Dominik Haumann 2010-06-20 11:44:08 UTC

Ok, this is just about spit view: If you start kate and splitted views are restored, you always get that. If you click in all views once, all works fine atain.

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