| Summary: | Hot keys get unbound and switch to terminals | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | Jonathan Cervidae <M8R-a46k7l> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | andresbajotierra, kde |
| Priority: | NOR | Keywords: | investigated, triaged |
| Version: | 4.2.2 | ||
| Target Milestone: | --- | ||
| Platform: | RedHat Enterprise Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jonathan Cervidae
2009-05-14 13:14:46 UTC
Alt+F4 to close applications suffers the same problem so I'm assuming all the Alt+FKEY combinations do. Are any other keys being stuck some times ? (like letters when you type?) Thanks No keys are getting stuck, it is simply that whatever hook causes the ALT+FKEY to change to terminals regains priority after it is used. I said so because I'm sometimes experiencing about some keys being stuck.. and I though about Control being stucked. (so just pressing Alt+F1 would lead to Ctrl+Alt+F1 and switching to VT1). No clues This just happened to me in a new session where I had not changed to any console virtual terminals. I really do not know if it is a KDM or X issue or what, nor how to debug it. I assume that there is some sort of keyboard driver in the kernel? Well if I did a conditional breakpoint upon hitting crtl+fkey and then stepped into the functions that happened would I find the bug? This sort of wizardry is way beyond me it's just a vague idea and if someone has a URL which would give me a "crash course" in how to do that sort of thing then I will do it myself. @Jonathan Is that reproducible for you? If yes start xev after switching back to your x session and see what x11 thinks you pressed. xkbwatch could be helpful too as it shows if x11 thinks an modifier is pressed. If you start it after switching back and something is highlighted there x11 has an key stuck. This ctrl+alt+f2 key is in no way related to kde. So i would say this problem is not a kde problem but a x11 problem. Waiting for info for quite some time. 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 set the bug status 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! |