Setxkbmap turns off NumLock LED - but not NumLock
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
Whenever I use setxkbmap in a terminal (or my .bashrc), the next time I press any modifier keys (ctrl, shift, alt) the NumLock LED on my keyboard goes off, but NumLock itself is still active so it's in some kind of inconsistent state.
If I now press NumLock, the LED stays off but NumLock turns off, and a second press on NumLock turns both the numpad and the LED on again. Curiously, while the LED is in this inconsistent state, pressing caps lock turns both the NumLock and CapsLock LEDs on.
The command that I have in my .bashrc causing this is setxkbmap -option compose:ralt but it also happens if I issue a plain setxkbmap with no parameters, or do anything else with that command.
Why is this happening (and am I doing something wrong)?
Dump of Xorg -version(I'm running Xubuntu/XFCE):
X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-30-server x86_64 Ubuntu
Current Operating System: Linux xxxxx 2.6.32-41-generic #94-Ubuntu SMP Fri Jul 6 18:00:34 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-41-generic root=UUID=xxxxx ro quiet splash
Build Date: 25 February 2012 06:57:33AM
xorg-server 2:1.7.6-2ubuntu7.11 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.16.4
x11 keyboard xkb numlock
edited Nov 26 at 1:00
Rui F Ribeiro
38.3k1477127
asked Aug 8 '12 at 9:41
Bristol
63749
add a comment |
up vote
2
down vote
favorite
Whenever I use setxkbmap in a terminal (or my .bashrc), the next time I press any modifier keys (ctrl, shift, alt) the NumLock LED on my keyboard goes off, but NumLock itself is still active so it's in some kind of inconsistent state.
If I now press NumLock, the LED stays off but NumLock turns off, and a second press on NumLock turns both the numpad and the LED on again. Curiously, while the LED is in this inconsistent state, pressing caps lock turns both the NumLock and CapsLock LEDs on.
The command that I have in my .bashrc causing this is setxkbmap -option compose:ralt but it also happens if I issue a plain setxkbmap with no parameters, or do anything else with that command.
Why is this happening (and am I doing something wrong)?
Dump of Xorg -version(I'm running Xubuntu/XFCE):
X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-30-server x86_64 Ubuntu
Current Operating System: Linux xxxxx 2.6.32-41-generic #94-Ubuntu SMP Fri Jul 6 18:00:34 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-41-generic root=UUID=xxxxx ro quiet splash
Build Date: 25 February 2012 06:57:33AM
xorg-server 2:1.7.6-2ubuntu7.11 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.16.4
x11 keyboard xkb numlock
edited Nov 26 at 1:00
Rui F Ribeiro
38.3k1477127
asked Aug 8 '12 at 9:41
Bristol
63749
FWIW, I am seeing the exact same issue on X.Org X Server 1.13.0 (vanilla Ubuntu 12.04.2, Das Keyboard P/N DKI-USB). Possibly related bug report.
– l0b0
Apr 10 '13 at 11:38
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Whenever I use setxkbmap in a terminal (or my .bashrc), the next time I press any modifier keys (ctrl, shift, alt) the NumLock LED on my keyboard goes off, but NumLock itself is still active so it's in some kind of inconsistent state.
If I now press NumLock, the LED stays off but NumLock turns off, and a second press on NumLock turns both the numpad and the LED on again. Curiously, while the LED is in this inconsistent state, pressing caps lock turns both the NumLock and CapsLock LEDs on.
The command that I have in my .bashrc causing this is setxkbmap -option compose:ralt but it also happens if I issue a plain setxkbmap with no parameters, or do anything else with that command.
Why is this happening (and am I doing something wrong)?
Dump of Xorg -version(I'm running Xubuntu/XFCE):
X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-30-server x86_64 Ubuntu
Current Operating System: Linux xxxxx 2.6.32-41-generic #94-Ubuntu SMP Fri Jul 6 18:00:34 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-41-generic root=UUID=xxxxx ro quiet splash
Build Date: 25 February 2012 06:57:33AM
xorg-server 2:1.7.6-2ubuntu7.11 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.16.4
x11 keyboard xkb numlock
edited Nov 26 at 1:00
Rui F Ribeiro
38.3k1477127
asked Aug 8 '12 at 9:41
Bristol
63749
Whenever I use setxkbmap in a terminal (or my .bashrc), the next time I press any modifier keys (ctrl, shift, alt) the NumLock LED on my keyboard goes off, but NumLock itself is still active so it's in some kind of inconsistent state.
If I now press NumLock, the LED stays off but NumLock turns off, and a second press on NumLock turns both the numpad and the LED on again. Curiously, while the LED is in this inconsistent state, pressing caps lock turns both the NumLock and CapsLock LEDs on.
The command that I have in my .bashrc causing this is setxkbmap -option compose:ralt but it also happens if I issue a plain setxkbmap with no parameters, or do anything else with that command.
Why is this happening (and am I doing something wrong)?
Dump of Xorg -version(I'm running Xubuntu/XFCE):
X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-30-server x86_64 Ubuntu
Current Operating System: Linux xxxxx 2.6.32-41-generic #94-Ubuntu SMP Fri Jul 6 18:00:34 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-41-generic root=UUID=xxxxx ro quiet splash
Build Date: 25 February 2012 06:57:33AM
xorg-server 2:1.7.6-2ubuntu7.11 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.16.4
x11 keyboard xkb numlock
x11 keyboard xkb numlock
edited Nov 26 at 1:00
Rui F Ribeiro
38.3k1477127
asked Aug 8 '12 at 9:41
Bristol
63749
edited Nov 26 at 1:00
Rui F Ribeiro
38.3k1477127
asked Aug 8 '12 at 9:41
Bristol
63749
edited Nov 26 at 1:00
Rui F Ribeiro
38.3k1477127
edited Nov 26 at 1:00
Rui F Ribeiro
38.3k1477127
edited Nov 26 at 1:00
Rui F Ribeiro
38.3k1477127
38.3k1477127
asked Aug 8 '12 at 9:41
Bristol
63749
asked Aug 8 '12 at 9:41
Bristol
63749
asked Aug 8 '12 at 9:41
Bristol
63749
63749
FWIW, I am seeing the exact same issue on X.Org X Server 1.13.0 (vanilla Ubuntu 12.04.2, Das Keyboard P/N DKI-USB). Possibly related bug report.
– l0b0
Apr 10 '13 at 11:38
add a comment |
FWIW, I am seeing the exact same issue on X.Org X Server 1.13.0 (vanilla Ubuntu 12.04.2, Das Keyboard P/N DKI-USB). Possibly related bug report.
– l0b0
Apr 10 '13 at 11:38
FWIW, I am seeing the exact same issue on X.Org X Server 1.13.0 (vanilla Ubuntu 12.04.2, Das Keyboard P/N DKI-USB). Possibly related bug report.
– l0b0
Apr 10 '13 at 11:38
FWIW, I am seeing the exact same issue on X.Org X Server 1.13.0 (vanilla Ubuntu 12.04.2, Das Keyboard P/N DKI-USB). Possibly related bug report.
– l0b0
Apr 10 '13 at 11:38
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
Looks like this quote explains it:
Warning. setxkbmap not only alters the alphanumeric keys to the values given in the map; it also resets all other keys to the startup default. If you have assigned values to the Windows keys or the multimedia keys, these settings may be lost.
Since the default visual and system (or "actual") state of the Num Lock key presumably is off, I'm guessing that's why this happens at all. Why the system state is untouched and why this only happens when pressing certain keys is still a mystery.
answered Apr 10 '13 at 11:44
l0b0
27.3k17112239
add a comment |
up vote
1
down vote
This bug sucks big time. I've reported upstream at https://bugs.freedesktop.org/show_bug.cgi?id=78012.
As long as you're invoking setxkbmap from a script, you can work it around by executing "numlockx off; numlockx on" afterwards. But you can't do this if you're using a desktop hotkey (e.g. Alt+Shift).
answered Apr 27 '14 at 20:51
egmont
2,5411912
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Looks like this quote explains it:
Warning. setxkbmap not only alters the alphanumeric keys to the values given in the map; it also resets all other keys to the startup default. If you have assigned values to the Windows keys or the multimedia keys, these settings may be lost.
Since the default visual and system (or "actual") state of the Num Lock key presumably is off, I'm guessing that's why this happens at all. Why the system state is untouched and why this only happens when pressing certain keys is still a mystery.
answered Apr 10 '13 at 11:44
l0b0
27.3k17112239
add a comment |
up vote
1
down vote
Looks like this quote explains it:
Warning. setxkbmap not only alters the alphanumeric keys to the values given in the map; it also resets all other keys to the startup default. If you have assigned values to the Windows keys or the multimedia keys, these settings may be lost.
Since the default visual and system (or "actual") state of the Num Lock key presumably is off, I'm guessing that's why this happens at all. Why the system state is untouched and why this only happens when pressing certain keys is still a mystery.
answered Apr 10 '13 at 11:44
l0b0
27.3k17112239
add a comment |
up vote
1
down vote
up vote
1
down vote
Looks like this quote explains it:
Warning. setxkbmap not only alters the alphanumeric keys to the values given in the map; it also resets all other keys to the startup default. If you have assigned values to the Windows keys or the multimedia keys, these settings may be lost.
Since the default visual and system (or "actual") state of the Num Lock key presumably is off, I'm guessing that's why this happens at all. Why the system state is untouched and why this only happens when pressing certain keys is still a mystery.
answered Apr 10 '13 at 11:44
l0b0
27.3k17112239
Looks like this quote explains it:
Warning. setxkbmap not only alters the alphanumeric keys to the values given in the map; it also resets all other keys to the startup default. If you have assigned values to the Windows keys or the multimedia keys, these settings may be lost.
Since the default visual and system (or "actual") state of the Num Lock key presumably is off, I'm guessing that's why this happens at all. Why the system state is untouched and why this only happens when pressing certain keys is still a mystery.
answered Apr 10 '13 at 11:44
l0b0
27.3k17112239
answered Apr 10 '13 at 11:44
l0b0
27.3k17112239
answered Apr 10 '13 at 11:44
l0b0
27.3k17112239
answered Apr 10 '13 at 11:44
l0b0
27.3k17112239
27.3k17112239
add a comment |
add a comment |
up vote
1
down vote
This bug sucks big time. I've reported upstream at https://bugs.freedesktop.org/show_bug.cgi?id=78012.
As long as you're invoking setxkbmap from a script, you can work it around by executing "numlockx off; numlockx on" afterwards. But you can't do this if you're using a desktop hotkey (e.g. Alt+Shift).
answered Apr 27 '14 at 20:51
egmont
2,5411912
add a comment |
up vote
1
down vote
This bug sucks big time. I've reported upstream at https://bugs.freedesktop.org/show_bug.cgi?id=78012.
As long as you're invoking setxkbmap from a script, you can work it around by executing "numlockx off; numlockx on" afterwards. But you can't do this if you're using a desktop hotkey (e.g. Alt+Shift).
answered Apr 27 '14 at 20:51
egmont
2,5411912
add a comment |
up vote
1
down vote
up vote
1
down vote
This bug sucks big time. I've reported upstream at https://bugs.freedesktop.org/show_bug.cgi?id=78012.
As long as you're invoking setxkbmap from a script, you can work it around by executing "numlockx off; numlockx on" afterwards. But you can't do this if you're using a desktop hotkey (e.g. Alt+Shift).
answered Apr 27 '14 at 20:51
egmont
2,5411912
This bug sucks big time. I've reported upstream at https://bugs.freedesktop.org/show_bug.cgi?id=78012.
As long as you're invoking setxkbmap from a script, you can work it around by executing "numlockx off; numlockx on" afterwards. But you can't do this if you're using a desktop hotkey (e.g. Alt+Shift).
answered Apr 27 '14 at 20:51
egmont
2,5411912
answered Apr 27 '14 at 20:51
egmont
2,5411912
answered Apr 27 '14 at 20:51
egmont
2,5411912
answered Apr 27 '14 at 20:51
egmont
2,5411912
2,5411912
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%2f45010%2fsetxkbmap-turns-off-numlock-led-but-not-numlock%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
FWIW, I am seeing the exact same issue on X.Org X Server 1.13.0 (vanilla Ubuntu 12.04.2, Das Keyboard P/N DKI-USB). Possibly related bug report.
– l0b0
Apr 10 '13 at 11:38