Post #5517: Thanks for the technical info on what’s happening. It’s reassuring that the mech
📋 Metadata
- Author: groomedmonkey
- Date: 2025-07-06 09:04:55
- Type:
discussion - Quality Score: 7/10
- Reply to: post_05516
- Replies (1): post_05518
🏷️ Tags
hotkeys configuration conflicts advanced unsolved
⚙️ Related PME Features
- Hotkey Configuration
💬 Content
Thanks for the technical info on what’s happening. It’s reassuring that the mechanism for why it happens is known. 
core devs can provide better tools to begin fixing issues like this.
Unfortunately, the keymap duplication bug is at least 10 years old with earliest bug report I found for version 2.7.5 and several currently open ones. Frustratingly, this means it doesn’t impact enough people, or the right people, for it to be properly addressed (feels like the whole keymap system needs a re-design and rebuild).
If you can nail down the reproduction steps, sharing them here would help others avoid the issue and potentially lead to a proper fix.
I’ll do my best to investigate, and post back with any findings, when I start a new config journey after this current project. I’m not hopeful though, as it might be hard to figure out how to repro. But since I have at least two ghost keys, maybe I have “the touch”.
@fjg3d Yeah native import/export but I gave up as I was exporting versions and didn’t notice that importing (when I wanted to undo a key-mapping experiment) seemed to exacerbate the duplication problem; I now have 100s of duplicates that mostly don’t cause problems but annoy me greatly and make it impossible to manage sensibly. I plan to export and clean my keymap config manually. People say this is an act of folly so I might have to settle with just using it to figure out what my customisations are and documenting them. If anyone has any battle-tested tips…
Maybe, one day, my Blender keymap file will be the immutable source of truth.
❤️ 3 likes