https://bugs.kde.org/show_bug.cgi?id=456958
--- Comment #10 from Nicolas Fella <nicolas.fe...@gmx.de> --- The problem here is somewhat fundamental to the way kglobalaccel works. Therefore I'm very hesitant to just remove the SimpleConfig flag hoping it will fix everything. When a program registers a global shortcut it does that by calling e.g. KGlobalAccel::self()->setGlobalShortcut(). That will register the shortcut and its associated metadata (internal and user-facing name etc) with klgobalacceld. kglobalacceld then saves that information to kglobalshortcutsrc and loads it again on the next start. Any user modifications are also saved to kglobalshortcutsrc. This causes a behavior of kglobalshortcutsrc that is very different to typical config files. Usually when you never changed any particular setting the relevant file in ~/.config is empty and system-wide or buildin defaults apply. But here you will find that .config/kglobalshortcutsrc is always populated with stuff, even if you never changed anything. The current approacj is quite messy and causes problems (such as this). There is the idea of making shortcut definition more declarative by using per-component desktop files (see https://phabricator.kde.org/T12063). This could probably also help with enabling distro customization like you are asking for -- You are receiving this mail because: You are watching all bug changes.
