Weird default binding and can't change those default binding

[Louisina-TSS]

Hello

I jut bought the Steelseries Apex ("normal" version (not Raw)) and I have some problems with the extra-keys. I was looking for some infos on the net, but the only one answer founded is "rebind with xbindkeys or gnome/KDE gui system", but that doesn't work on my laptop: the keys are always set to their old config, and MX keys (left) have the same scancode and keycode than the mediakeys (right).

If I edit the .Xmodmap file to set "F13>34", idem, the keyconfig is always the old config and gnome GUI system see the modifications.

I don't know how fix that or which script launch. Anyone can help me plz ? Thx

(PS: My spacebar and some keys like Maj doesn't answer sometimes if I don't smash them at the center of the key. Do you have the same hardware problem ?)

[kiwistrongis]

Hey there. Make sure you're running xmodmap ~/.Xmodmap after editing it to apply your changes. My own installation has actually been broken for a while too, but I haven't spent any time trying to fix it. I have a feeling its due to a systemd update, but idk. Maybe I'll spend some time on the weekend looking into it.

[kiwistrongis]

Oh, by the way, you might wanna merge this: phortx/apexctl-git-aur#1

[Louisina-TSS]

Hello Thx for the reply.

I aleady modificate ~/.Xmodmap to this. When I don't run xmodmap ~/.Xmodmap, the extra keys work as their default config (MX10 & 11 activate/desactivate my touchpad for instance), and when I run xmodmap ~/.Xmodmap, when I try to bind those keys (to a custom shortcut), I see "Fx" but still work as their default config.

!! begin ApexCtl

! MX keys keycode 179 = F25 keycode 180 = F26 keycode 181 = F27 keycode 182 = F28 keycode 183 = F29 keycode 184 = F30 keycode 185 = F31 keycode 186 = F32 keycode 187 = F33 keycode 188 = F34

! M keys keycode 191 = F13 keycode 192 = F14 keycode 193 = F15 keycode 194 = F16 keycode 195 = F17 keycode 196 = F18 keycode 197 = F19 keycode 198 = F20 keycode 199 = F21 keycode 200 = F22 keycode 201 = F23 keycode 202 = F24

! back/forward keys !keycode 000 = Back !keycode 000 = Forward

!! end ApexCtl

---

PS: What is your script ?

[kiwistrongis]

Whoopsie wrong convo aha. Ignore the "you might wanna merge this" comment.

I'm really just using this for the pretty colours right now. I normally invoke it from this little bash alias:

apex-profile(){
    sudo apexctl colors \
        -s b820a8:8 \
        -n ec1210:8 \
        -e 20f830:8 \
        -w 30a8a0:8 \
        -l c80808:5
}

apex(){
    xmodmap ~/.Xmodmap
    apex-profile
    echo "Apex enabled"
}

So when I login, I just open a terminal, type apex, and move on with my life.

[Louisina-TSS]

Wow... I try to reinstall apexctl but it's installed in /asdf/usr/bin/apexctl instead of the good old /usr/local/bin folder O.O

(Founded, it's a like in the makefile which I don't have in the old version L9. "INSTALL_ROOT ?= /asdf". I try to remove it before make)

PS: I make a bash file like yours, but when I try to run it, I have "ApexBase: line 15: Syntax Error : premature end of file" (line 15 is at the end of the bash file) (my message isn't in english, so I translate it, idk it's the right translation)

PPS: just "xmodmap ~/.Xmodmap" commant don't activate the keys without a "sudo apexctl" command. And that doesn't work (I have "0xf8" at least on M12 & M11)

PPPS: Do you have the same problem with the spacebar which doesn't answer without SMASH it ? Or it's a physical problem and I have a damaged keyboard ?)

[kiwistrongis]

Ah, thanks for pointing out the install root issue... my bad. I'll fix it tonight. Regarding the other things:

• Post a gist of your script ( gist.github.com ). I'll tell you what's wrong with it.
• This M_, MX_, and L* key activation part of this project isn't currently working. Sorry bro.
• My spacebar is totally fine. Once again, sorry man :(.

[Louisina-TSS]

You mean the working part of this script is the color feature and the "activation default special keys" without modification not working ? :( That's sad... But why do you talk about modifications on Xmodmap if we can't remap the extra-keys of the keyboard ? (for the spacebar, I have the same problem with the MAJ key, it's active only when I press it with lot of weight. It's probably a hardware problem)

[tuxmark5]

@Tameiki Xmodmap maps logical keys that X11 understands (F13, F14 and so on) to hardware ids. If you don't update your Xmodmap, some of the additional keys overlap with existing keys (mostly various media buttons). udev rules and Xmodmap file ensures that all additional keys do not duplicate and have more or less meaningful names assigned to them.

You could use some keys without using udev rules or Xmodmap keys, but then X11 server won't recognize some of the keys.

Regarding your space issue, yes, that does sound like a hardware problem.

[Louisina-TSS]

Hello @tuxmark5 ^_^

So is it "technically" possible to map the extra-keys (M, MX and L*) to F13>34 ? And "separate" them from media-keys or other keys ? (like I read on other "issues" on github) Or it's the goal of ApexCtl but not really working ? (Sry, I don't understand if the extra-keys feature working with lot of modifications (udev, Xmodmap, etc...) or just not working yet)

(Or maybe I'm just a noob who fail the ApexCtl installation... That also possible .-. )