Summary: | Setting KP_Home as a separate key from Home | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Dotan Cohen <kde-2011.08> |
Component: | kcm_khotkeys | Assignee: | Michael Jansen <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | 1i5t5.duncan, justin.zobel |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dotan Cohen
2011-10-21 13:18:21 UTC
FWIW, here's the thread on the kde lists (gmane archive) dealing with this issue. http://comments.gmane.org/gmane.comp.kde.general/25267 I asked about a recent xkeyboard-config bug, but it doesn't seem to be related to that. I have the issue here too, after the xkeyboard-config patch mentioned. With numlock off, xev says KP_Home, unshifted, KP_7, shifted, but kde's hotkey setup UI reports Home and 7. With numlock on, xev reverses as expected (unshifted KP_Home, shifted KP_7), but kde's UI reports 7 and Shift+Home. Where's the KP_* distinctions? Thanks for the report Dotan. I've just tested this in systemsettings from git master and I am able to map shortcuts to those keys. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" when you respond, thanks. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |