Bug 352067 - new key binding does not work
Summary: new key binding does not work
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_khotkeys (other bugs)
Version First Reported In: 5.20.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-31 17:20 UTC by illumilore
Modified: 2024-03-04 19:42 UTC (History)
1 user (show)

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 illumilore 2015-08-31 17:20:16 UTC
When I right click on the kde start menu, then click app launcher settings, then the keyboard shortcut tabs, then I click "none" to set a new keyboard binding, I then hit ctrl+escape, but instead of it setting that to launch the start menu, it brings up the task manager.

Reproducible: Always
Comment 1 Thomas Lübking 2015-10-21 20:19:29 UTC
Git commit 1c28e9b9a8caf34643ae2a697415a0dfc8d1a8c3 by Thomas Lübking.
Committed on 21/10/2015 at 20:06.
Pushed by luebking into branch 'master'.

do not write back dated settings from daemon

when the kcm applies, it causes emits of shortcut change signals
this causes a save request in the daemon which then writes its
dated configuration before the kcm asks is to re-read the config

this would usually break changes of only the action or the shortcut

=> we have the kcm mark the updated config file and in the daemon
do not write the settings until it re-read it (where it removes the flag)

this is an IPC race and _not_ related to the previous delaying patch
which would at best mitigate the issue (but the kconfig sync delays too long)
REVIEW: 125630

M  +1    -0    app/kded.cpp
M  +12   -0    libkhotkeysprivate/settings.cpp
M  +2    -0    libkhotkeysprivate/settings.h

http://commits.kde.org/khotkeys/1c28e9b9a8caf34643ae2a697415a0dfc8d1a8c3
Comment 2 Thomas Lübking 2015-12-24 21:34:29 UTC
Still a problem after the patch?
Comment 3 illumilore 2015-12-26 01:20:12 UTC
What version of kde do I need for it to be patched?
Comment 4 Thomas Lübking 2016-01-31 10:47:45 UTC
frameworks 5.18 (release mid january) - sorry for not replying earlier, I'm not attached to these bugs.
Comment 5 Aleix Pol 2016-02-02 14:59:50 UTC
bump?

I'll mark as confirmed for now, as I understand found the issue, before fixing it.
Comment 6 Justin Zobel 2021-03-09 23:51:16 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 7 Nate Graham 2024-03-04 19:42:06 UTC
As announced in https://pointieststick.com/2023/07/26/what-we-plan-to-remove-in-plasma-6/ and https://community.kde.org/Plasma/Plasma_6#Removals, I'm afraid KHotKeys has reached end-of-life in Plasma 6. Accordingly, all bug reports and feature requests for it must be closed now.

Most of what KHotKeys could do can already be done with the newer KGlobalAccel system in Plasma 6. A few features such as mouse gestures and triggering conditions based on changes to window states are not yet implemented in the new system. These will be added in the future if and when resources materialize for them, and/or when a kind soul submits patches to implement them! :) Meanwhile, the 3rd-party "Mouse Actions" app (https://github.com/jersou/mouse-actions) may be usable for implementing your own mouse gestures again.

Thanks for your understanding, everyone.