Ctrl Alt AltGr keys not working on Ubuntu 16.04
1
I have a USB-gaming keyboard (bought on aliexpress sometime ago) with English keys. It works perfectly on Windows, even with the Spanish config.
The problem is that on Linux, the Ctrl Alt AltGr keys don't work, they are detected all as Left Shift keys. This is the xev exit:
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189078, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189150, (97,87), root:(1057,627),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189294, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189366, (97,87), root:(1057,627),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189990, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
This is the output of lsusb:
Bus 002 Device 004: ID 0c45:7603 Microdia
Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 003: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And this the output of xinput:
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PixArt USB Optical Mouse id=10 [slave pointer (2)]
⎜ ↳ SONiX USB Keyboard id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ GASIA USB MSN KB id=9 [slave keyboard (3)]
↳ SONiX USB Keyboard id=11 [slave keyboard (3)]
↳ Eee PC WMI hotkeys id=13 [slave keyboard (3)]
I use Ubuntutu 16.04, but in older versions the problem is the same. I've tried some fixes and using gnome tweak tool, but that didn't work.
Some ideas?
--Edited:
I just fixed it installing this driver https://bitbucket.org/Swoogan/aziokbd
Working on Ubuntu 18 64 bits.
16.04 keyboard shortcut-keys
asked Nov 10 '17 at 18:09
AdritekAdritek
62
add a comment |
1
I have a USB-gaming keyboard (bought on aliexpress sometime ago) with English keys. It works perfectly on Windows, even with the Spanish config.
The problem is that on Linux, the Ctrl Alt AltGr keys don't work, they are detected all as Left Shift keys. This is the xev exit:
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189078, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189150, (97,87), root:(1057,627),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189294, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189366, (97,87), root:(1057,627),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189990, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
This is the output of lsusb:
Bus 002 Device 004: ID 0c45:7603 Microdia
Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 003: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And this the output of xinput:
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PixArt USB Optical Mouse id=10 [slave pointer (2)]
⎜ ↳ SONiX USB Keyboard id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ GASIA USB MSN KB id=9 [slave keyboard (3)]
↳ SONiX USB Keyboard id=11 [slave keyboard (3)]
↳ Eee PC WMI hotkeys id=13 [slave keyboard (3)]
I use Ubuntutu 16.04, but in older versions the problem is the same. I've tried some fixes and using gnome tweak tool, but that didn't work.
Some ideas?
--Edited:
I just fixed it installing this driver https://bitbucket.org/Swoogan/aziokbd
Working on Ubuntu 18 64 bits.
16.04 keyboard shortcut-keys
asked Nov 10 '17 at 18:09
AdritekAdritek
62
I presume the keyboard is connected via USB. Could you please edit your question to include the output oflsusbandxinput? Thanks.
– David Foerster
Nov 11 '17 at 8:39
there's a thread at ubuntuforums that references theMicrodiadevice seen in yourlsusboutput (apparently theSONiXdevice in thexinputoutput, as opposed to theGreenAsiaandGASIAentries).
– quixotic
Nov 13 '17 at 22:54
add a comment |
1
1
1
I have a USB-gaming keyboard (bought on aliexpress sometime ago) with English keys. It works perfectly on Windows, even with the Spanish config.
The problem is that on Linux, the Ctrl Alt AltGr keys don't work, they are detected all as Left Shift keys. This is the xev exit:
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189078, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189150, (97,87), root:(1057,627),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189294, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189366, (97,87), root:(1057,627),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189990, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
This is the output of lsusb:
Bus 002 Device 004: ID 0c45:7603 Microdia
Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 003: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And this the output of xinput:
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PixArt USB Optical Mouse id=10 [slave pointer (2)]
⎜ ↳ SONiX USB Keyboard id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ GASIA USB MSN KB id=9 [slave keyboard (3)]
↳ SONiX USB Keyboard id=11 [slave keyboard (3)]
↳ Eee PC WMI hotkeys id=13 [slave keyboard (3)]
I use Ubuntutu 16.04, but in older versions the problem is the same. I've tried some fixes and using gnome tweak tool, but that didn't work.
Some ideas?
--Edited:
I just fixed it installing this driver https://bitbucket.org/Swoogan/aziokbd
Working on Ubuntu 18 64 bits.
16.04 keyboard shortcut-keys
asked Nov 10 '17 at 18:09
AdritekAdritek
62
I have a USB-gaming keyboard (bought on aliexpress sometime ago) with English keys. It works perfectly on Windows, even with the Spanish config.
The problem is that on Linux, the Ctrl Alt AltGr keys don't work, they are detected all as Left Shift keys. This is the xev exit:
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189078, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189150, (97,87), root:(1057,627),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189294, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189366, (97,87), root:(1057,627),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x2800001,
root 0xcd, subw 0x0, time 189990, (97,87), root:(1057,627),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
This is the output of lsusb:
Bus 002 Device 004: ID 0c45:7603 Microdia
Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 003: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And this the output of xinput:
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PixArt USB Optical Mouse id=10 [slave pointer (2)]
⎜ ↳ SONiX USB Keyboard id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ GASIA USB MSN KB id=9 [slave keyboard (3)]
↳ SONiX USB Keyboard id=11 [slave keyboard (3)]
↳ Eee PC WMI hotkeys id=13 [slave keyboard (3)]
I use Ubuntutu 16.04, but in older versions the problem is the same. I've tried some fixes and using gnome tweak tool, but that didn't work.
Some ideas?
--Edited:
I just fixed it installing this driver https://bitbucket.org/Swoogan/aziokbd
Working on Ubuntu 18 64 bits.
16.04 keyboard shortcut-keys
16.04 keyboard shortcut-keys
asked Nov 10 '17 at 18:09
AdritekAdritek
62
asked Nov 10 '17 at 18:09
AdritekAdritek
62
edited 14 mins ago
Adritek
asked Nov 10 '17 at 18:09
AdritekAdritek
62
asked Nov 10 '17 at 18:09
AdritekAdritek
62
asked Nov 10 '17 at 18:09
AdritekAdritek
62
62
I presume the keyboard is connected via USB. Could you please edit your question to include the output oflsusbandxinput? Thanks.
– David Foerster
Nov 11 '17 at 8:39
there's a thread at ubuntuforums that references theMicrodiadevice seen in yourlsusboutput (apparently theSONiXdevice in thexinputoutput, as opposed to theGreenAsiaandGASIAentries).
– quixotic
Nov 13 '17 at 22:54
add a comment |
I presume the keyboard is connected via USB. Could you please edit your question to include the output oflsusbandxinput? Thanks.
– David Foerster
Nov 11 '17 at 8:39
there's a thread at ubuntuforums that references theMicrodiadevice seen in yourlsusboutput (apparently theSONiXdevice in thexinputoutput, as opposed to theGreenAsiaandGASIAentries).
– quixotic
Nov 13 '17 at 22:54
I presume the keyboard is connected via USB. Could you please edit your question to include the output of
lsusb and xinput? Thanks.– David Foerster
Nov 11 '17 at 8:39
I presume the keyboard is connected via USB. Could you please edit your question to include the output of
lsusb and xinput? Thanks.– David Foerster
Nov 11 '17 at 8:39
there's a thread at ubuntuforums that references the
Microdia device seen in your lsusb output (apparently the SONiX device in the xinput output, as opposed to the GreenAsia and GASIA entries).– quixotic
Nov 13 '17 at 22:54
there's a thread at ubuntuforums that references the
Microdia device seen in your lsusb output (apparently the SONiX device in the xinput output, as opposed to the GreenAsia and GASIA entries).– quixotic
Nov 13 '17 at 22:54
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
draft saved
draft discarded
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%2faskubuntu.com%2fquestions%2f975147%2fctrl-alt-altgr-keys-not-working-on-ubuntu-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- 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.
draft saved
draft discarded
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%2faskubuntu.com%2fquestions%2f975147%2fctrl-alt-altgr-keys-not-working-on-ubuntu-16-04%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
I presume the keyboard is connected via USB. Could you please edit your question to include the output of
lsusbandxinput? Thanks.– David Foerster
Nov 11 '17 at 8:39
there's a thread at ubuntuforums that references the
Microdiadevice seen in yourlsusboutput (apparently theSONiXdevice in thexinputoutput, as opposed to theGreenAsiaandGASIAentries).– quixotic
Nov 13 '17 at 22:54