https://bugs.kde.org/show_bug.cgi?id=518683
Noah Davis <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Latest Commit| |https://invent.kde.org/fram | |eworks/kconfig/-/commit/0fd | |33d70928864758fb394c8ec8e20 | |b384205acd Resolution|--- |FIXED Version| |6.30 Fixed/Implemented| | In| | --- Comment #10 from Noah Davis <[email protected]> --- Git commit 0fd33d70928864758fb394c8ec8e20b384205acd by Noah Davis. Committed on 05/09/2026 at 13:30. Pushed by ndavis into branch 'master'. KStandardShortcut: Fix using a null key sequence for removed shortcuts Currently, removing a shortcut in system settings sets its string value in kdeglobals to an empty string. It may have been that we set the value to "none" in the past, but not anymore. Since the code before this patch only checked for "none", the empty string was converted to a null character key and KStandardShortcuts would give a null key sequence for the removed shortcut. This would cause disabled keys to trigger the removed shortcut since disabled keys can still send null character key events. For backwards compatibility, it may be a good idea to keep the check for "none". Example of how removed shortcuts are currently set in kdeglobals: ``` [Shortcuts] Help= ``` FIXED-IN: 6.30 M +48 -0 autotests/kstandardshortcutwatchertest.cpp M +1 -1 src/gui/kstandardshortcut.cpp https://invent.kde.org/frameworks/kconfig/-/commit/0fd33d70928864758fb394c8ec8e20b384205acd -- You are receiving this mail because: You are watching all bug changes.
