Bug 274155 - Shortcut keys don't work sometimes (after upgrade from KDE 3?)
Summary: Shortcut keys don't work sometimes (after upgrade from KDE 3?)
Status: RESOLVED DUPLICATE of bug 188764
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 23:43 UTC by Milko Krachounov
Modified: 2011-06-28 19:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milko Krachounov 2011-05-25 23:43:19 UTC
Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

When I upgraded to KDE 4.1 (or 4.2, I don't remember) from KDE 3.5.x, none of the keyboard shortcuts worked, and I got error messages like:

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

I had to change Ctrl+S to something else and back to get it to work. After a few versions, I didn't have to do it any more - changing the shortcut once made it work on every following restart of Kate.

Since then, the same error occurred to me once or twice, but it was gone after changing the shortcut or restarting Kate, until today when I closed a Kate session and opened it again, and, voila, no shortcut combinations work. Every time I get:

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

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

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

Neither restarting Kate nor changing them seems to fix it.

I've had this problem on Gentoo and Debian so far.

Reproducible: Sometimes
Comment 1 Milko Krachounov 2011-05-25 23:49:25 UTC
Oh, my mistake: Changing the shortcut to another key and back doesn't solve the problem and *never did*, I have to change the shortcut to the same key (e.g. if the default shortcut for Find is Ctrl+F, I choose a custom one and press Ctrl+F), it tells me that it is already in use by another action, and I tell it to move it to this action. When I do this I stop getting the error for this shortcut and for any other too.

Also this is what fixed it every time, and it's possible that it never worked by just restarting Kate. And it's likely that the incidents are uniformly distributed over time since KDE 4.1/4.2, and not grouped around the first releases as I hinted in the first post.

Sorry for my bad memory, I'm bad at remembering something that happened so long ago.
Comment 2 Dominik Haumann 2011-06-25 09:47:02 UTC
Milko, are you using split views in Kate?
Comment 3 Milko Krachounov 2011-06-27 15:58:19 UTC
Yes.
Comment 4 Dominik Haumann 2011-06-28 19:32:08 UTC
Ok, then it's a very well known issue...

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