Bug 353695

Summary:	All shortcuts are ambigious suddenly
Product:	[Frameworks and Libraries] frameworks-kxmlgui	Reporter:	H.H. <cyberbeat>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	christoph, kde
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description H.H. 2015-10-08 22:14:59 UTC

I have installed kwrite-15.0.4.3, libkf5xmlgui-5.14.0,..
What I did:
I changed the shortcut in systemsettings=>shortcuts from ctrl+shift+z (redo) to ctrl+y
After that all shortcuts in kwrite (ctrl+c, ctrl+f,...) don't work anymore (ambigious message).
Restart/Kde-Relogin/.. does not help.

I did notice a perhaps relevant bug https://bugs.kde.org/show_bug.cgi?id=345411, but it should be fixed in my version, right?

Reproducible: Always

Comment 1 Christoph Cullmann 2015-10-09 07:43:06 UTC

It should be fixed, in any case that is an kxmlgui problem I think.

Comment 2 H.H. 2015-10-09 14:29:18 UTC

may there be a workaround for this? I cannot work anymore. even simple keys like "end" and "pos1" don't work anymore!

Comment 3 H.H. 2015-10-15 21:19:39 UTC

Please help me, which files do I have to delete, that the settings are restored, as a workaround. For every shortcut, there is the (wrong) message (example):

>Der Kurzbefehl „Ctrl+C“ ist doppeldeutig. Rufen Sie bitte „Einstellungen“ -> „Kurzbefehle festlegen“
>im Menü auf und beheben Sie den Konflikt.
>Es wird keine Aktion ausgeführt.

Comment 4 sedrubal 2016-01-21 17:56:43 UTC

Sometimes it helps to open the shortcut settings ("Settings">"Configure Shortcuts"), got to the action which is currently not working anymore, insert the expected shortcut even it is already inserted (or even if it is the default shortcut), a dialogue appears complaining about that the shortcut is already used for another action, hit "Reassign".

Sometimes you have to do it more than one time, and sometimes you can use the shortcut again, but sometimes not. This is quite nasty...

Comment 5 Christoph Feck 2017-03-01 00:29:53 UTC


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