“k” key sends focus in event
After a dist-upgrade to wheezy, my "k"-Key misbehaves. When typed in a gnome-terminal, no "k" is printed. Instead the terminal seems to grab the focus and will not release it. If I drag-down the mouse outside the terminal it highlights line inside the terminal. Also regular mouse clicks no longer work.
I ran xev an it shows three events when pressing "k"
- a FocusIn event
- a FocusOut event
- a KeymapNotify event
This only happens when I log in through a display manager using my account. It happens with gdm3 and wdm (I have not tested any others)
When I log in as a different user, the "k" key works.
When I log in through a display managaer using a "failsafe" session it also works. Other than that the issue occurs with many different session types.
When startig X from the commandline all is fine. The issue only occurs when logging in through a display manager.
AFAICS all other key work, including the uppercase shift-K
I looked for "dpkg-dist" files in /etc/X11 and only found the following:
./XftConfig.dpkg-dist
./rstart/config.dpkg-dist
So it appears to be related to something attached to my user account. In my dispair I renamed the ~/.config directory, but that didn't resolve the issue.
I am aware of p key doesn't work in X, and I believe it is the same issue, but I have no idea, where I could possibly have remapped the key or how to track this down.
debian xorg keyboard
edited Apr 13 '17 at 12:36
Community♦
1
asked Aug 6 '13 at 4:15
Martin Drautzburg
8081916
add a comment |
After a dist-upgrade to wheezy, my "k"-Key misbehaves. When typed in a gnome-terminal, no "k" is printed. Instead the terminal seems to grab the focus and will not release it. If I drag-down the mouse outside the terminal it highlights line inside the terminal. Also regular mouse clicks no longer work.
I ran xev an it shows three events when pressing "k"
- a FocusIn event
- a FocusOut event
- a KeymapNotify event
This only happens when I log in through a display manager using my account. It happens with gdm3 and wdm (I have not tested any others)
When I log in as a different user, the "k" key works.
When I log in through a display managaer using a "failsafe" session it also works. Other than that the issue occurs with many different session types.
When startig X from the commandline all is fine. The issue only occurs when logging in through a display manager.
AFAICS all other key work, including the uppercase shift-K
I looked for "dpkg-dist" files in /etc/X11 and only found the following:
./XftConfig.dpkg-dist
./rstart/config.dpkg-dist
So it appears to be related to something attached to my user account. In my dispair I renamed the ~/.config directory, but that didn't resolve the issue.
I am aware of p key doesn't work in X, and I believe it is the same issue, but I have no idea, where I could possibly have remapped the key or how to track this down.
debian xorg keyboard
edited Apr 13 '17 at 12:36
Community♦
1
asked Aug 6 '13 at 4:15
Martin Drautzburg
8081916
What window manager or desktop environment do you use? Does this still happen if you use a different one? Do you have a~/.Xmodmapor otherwise runxmodmapwhen you log in?
– Gilles
Aug 6 '13 at 20:34
add a comment |
After a dist-upgrade to wheezy, my "k"-Key misbehaves. When typed in a gnome-terminal, no "k" is printed. Instead the terminal seems to grab the focus and will not release it. If I drag-down the mouse outside the terminal it highlights line inside the terminal. Also regular mouse clicks no longer work.
I ran xev an it shows three events when pressing "k"
- a FocusIn event
- a FocusOut event
- a KeymapNotify event
This only happens when I log in through a display manager using my account. It happens with gdm3 and wdm (I have not tested any others)
When I log in as a different user, the "k" key works.
When I log in through a display managaer using a "failsafe" session it also works. Other than that the issue occurs with many different session types.
When startig X from the commandline all is fine. The issue only occurs when logging in through a display manager.
AFAICS all other key work, including the uppercase shift-K
I looked for "dpkg-dist" files in /etc/X11 and only found the following:
./XftConfig.dpkg-dist
./rstart/config.dpkg-dist
So it appears to be related to something attached to my user account. In my dispair I renamed the ~/.config directory, but that didn't resolve the issue.
I am aware of p key doesn't work in X, and I believe it is the same issue, but I have no idea, where I could possibly have remapped the key or how to track this down.
debian xorg keyboard
edited Apr 13 '17 at 12:36
Community♦
1
asked Aug 6 '13 at 4:15
Martin Drautzburg
8081916
After a dist-upgrade to wheezy, my "k"-Key misbehaves. When typed in a gnome-terminal, no "k" is printed. Instead the terminal seems to grab the focus and will not release it. If I drag-down the mouse outside the terminal it highlights line inside the terminal. Also regular mouse clicks no longer work.
I ran xev an it shows three events when pressing "k"
- a FocusIn event
- a FocusOut event
- a KeymapNotify event
This only happens when I log in through a display manager using my account. It happens with gdm3 and wdm (I have not tested any others)
When I log in as a different user, the "k" key works.
When I log in through a display managaer using a "failsafe" session it also works. Other than that the issue occurs with many different session types.
When startig X from the commandline all is fine. The issue only occurs when logging in through a display manager.
AFAICS all other key work, including the uppercase shift-K
I looked for "dpkg-dist" files in /etc/X11 and only found the following:
./XftConfig.dpkg-dist
./rstart/config.dpkg-dist
So it appears to be related to something attached to my user account. In my dispair I renamed the ~/.config directory, but that didn't resolve the issue.
I am aware of p key doesn't work in X, and I believe it is the same issue, but I have no idea, where I could possibly have remapped the key or how to track this down.
debian xorg keyboard
debian xorg keyboard
edited Apr 13 '17 at 12:36
Community♦
1
asked Aug 6 '13 at 4:15
Martin Drautzburg
8081916
edited Apr 13 '17 at 12:36
Community♦
1
asked Aug 6 '13 at 4:15
Martin Drautzburg
8081916
edited Apr 13 '17 at 12:36
Community♦
1
edited Apr 13 '17 at 12:36
Community♦
1
edited Apr 13 '17 at 12:36
Community♦
1
1
asked Aug 6 '13 at 4:15
Martin Drautzburg
8081916
asked Aug 6 '13 at 4:15
Martin Drautzburg
8081916
asked Aug 6 '13 at 4:15
Martin Drautzburg
8081916
8081916
What window manager or desktop environment do you use? Does this still happen if you use a different one? Do you have a~/.Xmodmapor otherwise runxmodmapwhen you log in?
– Gilles
Aug 6 '13 at 20:34
add a comment |
What window manager or desktop environment do you use? Does this still happen if you use a different one? Do you have a~/.Xmodmapor otherwise runxmodmapwhen you log in?
– Gilles
Aug 6 '13 at 20:34
What window manager or desktop environment do you use? Does this still happen if you use a different one? Do you have a
~/.Xmodmap or otherwise run xmodmap when you log in?– Gilles
Aug 6 '13 at 20:34
What window manager or desktop environment do you use? Does this still happen if you use a different one? Do you have a
~/.Xmodmap or otherwise run xmodmap when you log in?– Gilles
Aug 6 '13 at 20:34
add a comment |
2 Answers
2
active
oldest
votes
Meanwhile I found the answer:
In my case the display-managers start xbinkeys. When starting X from the commandline xbindkeys was (of course) not started. For some reason my .xbindkeysrc bound the letter "k".
The problem disappeared when I killed xbindkeys (which is not a permanent solution) or after I stripped down .xbindkeysrc.
answered Aug 9 '13 at 16:37
Martin Drautzburg
8081916
add a comment |
In my case, it was due to the leftover ibus config files from the previous version of Ubuntu. I removed them (located in ~/.config/ibus) and issued the following command to recreate the configs, and then logged out and logged in.
ibus reset-config
answered Dec 19 '18 at 12:24
Meghdad
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f85659%2fk-key-sends-focus-in-event%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Meanwhile I found the answer:
In my case the display-managers start xbinkeys. When starting X from the commandline xbindkeys was (of course) not started. For some reason my .xbindkeysrc bound the letter "k".
The problem disappeared when I killed xbindkeys (which is not a permanent solution) or after I stripped down .xbindkeysrc.
answered Aug 9 '13 at 16:37
Martin Drautzburg
8081916
add a comment |
Meanwhile I found the answer:
In my case the display-managers start xbinkeys. When starting X from the commandline xbindkeys was (of course) not started. For some reason my .xbindkeysrc bound the letter "k".
The problem disappeared when I killed xbindkeys (which is not a permanent solution) or after I stripped down .xbindkeysrc.
answered Aug 9 '13 at 16:37
Martin Drautzburg
8081916
add a comment |
Meanwhile I found the answer:
In my case the display-managers start xbinkeys. When starting X from the commandline xbindkeys was (of course) not started. For some reason my .xbindkeysrc bound the letter "k".
The problem disappeared when I killed xbindkeys (which is not a permanent solution) or after I stripped down .xbindkeysrc.
answered Aug 9 '13 at 16:37
Martin Drautzburg
8081916
Meanwhile I found the answer:
In my case the display-managers start xbinkeys. When starting X from the commandline xbindkeys was (of course) not started. For some reason my .xbindkeysrc bound the letter "k".
The problem disappeared when I killed xbindkeys (which is not a permanent solution) or after I stripped down .xbindkeysrc.
answered Aug 9 '13 at 16:37
Martin Drautzburg
8081916
answered Aug 9 '13 at 16:37
Martin Drautzburg
8081916
answered Aug 9 '13 at 16:37
Martin Drautzburg
8081916
answered Aug 9 '13 at 16:37
Martin Drautzburg
8081916
8081916
add a comment |
add a comment |
In my case, it was due to the leftover ibus config files from the previous version of Ubuntu. I removed them (located in ~/.config/ibus) and issued the following command to recreate the configs, and then logged out and logged in.
ibus reset-config
answered Dec 19 '18 at 12:24
Meghdad
1
add a comment |
In my case, it was due to the leftover ibus config files from the previous version of Ubuntu. I removed them (located in ~/.config/ibus) and issued the following command to recreate the configs, and then logged out and logged in.
ibus reset-config
answered Dec 19 '18 at 12:24
Meghdad
1
add a comment |
In my case, it was due to the leftover ibus config files from the previous version of Ubuntu. I removed them (located in ~/.config/ibus) and issued the following command to recreate the configs, and then logged out and logged in.
ibus reset-config
answered Dec 19 '18 at 12:24
Meghdad
1
In my case, it was due to the leftover ibus config files from the previous version of Ubuntu. I removed them (located in ~/.config/ibus) and issued the following command to recreate the configs, and then logged out and logged in.
ibus reset-config
answered Dec 19 '18 at 12:24
Meghdad
1
answered Dec 19 '18 at 12:24
Meghdad
1
answered Dec 19 '18 at 12:24
Meghdad
1
answered Dec 19 '18 at 12:24
Meghdad
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f85659%2fk-key-sends-focus-in-event%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What window manager or desktop environment do you use? Does this still happen if you use a different one? Do you have a
~/.Xmodmapor otherwise runxmodmapwhen you log in?– Gilles
Aug 6 '13 at 20:34