Arch Linux

chameleon_world

Member

Registered: 2019-06-10

Posts: 2

[Solved] Mod3 key always on due to CM Storm keyboard

Hello,

I have a CM Storm Devastator keyboard, and after I boot up my computer, I can't turn on the back-light for the keyboard on. I found this forum post - https://ubuntuforums.org/showthread.php?t=2208222 - which gave me a solution that works fine. BUT now that my Scroll Lock key is bound to Mod3, the Mod3 key is always on whenever my keyboard back-light is on, and this prevents me from using specific hotkeys. For instance, trying to use Ulauncher, if my back-light is on, pressing Ctrl+Space does nothing (because it's actually registering Ctrl+Mod3+Space) but if I turn my back-light off and press Ctrl+Space it opens Ulauncher as expected.

Do you know anyway around this? Should I just remap the Ulauncher hotkey to Ctrl+Mod3+Space? I feel like leaving this modifier key will cause more problems in the future with other hotkeys. Is there a better way to be able to turn my keyboard back-light on?

Thanks

Last edited by chameleon_world (2019-06-10 15:32:24)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [Solved] Mod3 key always on due to CM Storm keyboard

Ubuntu thread from five years ago?

Is this an Arch install?

Moving to NC...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,509

Re: [Solved] Mod3 key always on due to CM Storm keyboard

a) no "sudo", please. Counterproductive here.
b) "xset led" supports 32 values (1-32), try whether one of them alters the kbd backlight w/o further shenanigans
c) there's also "xmodmap remove …" which you might be able to use to clear the modifier mapping, but frankly, the script approach to first sleep (why?) then set the led and only afterwards manipulate the modifier map is probably too sophisticated for me…
(well, I could guess that it only works w/ the 2nd invocation after the intial mapping too place and all further equal calls to xmodmap are pointless and sleep is always a healthy thing…)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

chameleon_world

Member

Registered: 2019-06-10

Posts: 2

Re: [Solved] Mod3 key always on due to CM Storm keyboard

a) no "sudo", please. Counterproductive here.
b) "xset led" supports 32 values (1-32), try whether one of them alters the kbd backlight w/o further shenanigans
c) there's also "xmodmap remove …" which you might be able to use to clear the modifier mapping, but frankly, the script approach to first sleep (why?) then set the led and only afterwards manipulate the modifier map is probably too sophisticated for me…
(well, I could guess that it only works w/ the 2nd invocation after the intial mapping too place and all further equal calls to xmodmap are pointless and sleep is always a healthy thing…)

Ah! I tried just "xset led" and it turns my lights on. That's all I really needed. Thanks!