https://bugs.kde.org/show_bug.cgi?id=376859
--- Comment #6 from hardy.pub...@gmail.com --- The problem is still there but slightly different behaviour from what I recall. If the shortcut already exists, it correctly warns about the conflict with details about the conflict. If the shortcut does not exist, the stock warning appears as previously reported. -- You are receiving this mail because: You are watching all bug changes.
