Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

equal symbol is not working #20

Open
antoine-gallix opened this issue Nov 24, 2021 · 3 comments
Open

equal symbol is not working #20

antoine-gallix opened this issue Nov 24, 2021 · 3 comments

Comments

@antoine-gallix
Copy link

I'm using the extend layer option, after installing the xkb files on my system. All seems to work well on most applications, but the extend layer appears to break my "equal" symbol. The key doesn't produce any output on any of my applications. Strangely, the second level of the key, "+" works fine.
Looking at the output of xev I see that the key press event is not triggered, instead something else called KeymapNotify:

KeymapNotify event, serial 28, synthetic NO, window 0x0,
    keys:  4294967172 0   32  0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 28, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 1107135, (490,431), root:(490,460),
    state 0x0, keycode 21 (keysym 0x3d, equal), same_screen YES,
    XLookupString gives 1 bytes: (3d) "="
    XFilterEvent returns: False

And here is the output of xev for the shifted version, that produces a + without problem:

KeyPress event, serial 25, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 5845125, (399,579), root:(399,608),
    state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 28, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 5845311, (399,579), root:(399,608),
    state 0x1, keycode 21 (keysym 0x2b, plus), same_screen YES,
    XLookupString gives 1 bytes: (2b) "+"
    XmbLookupString gives 1 bytes: (2b) "+"
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 5845389, (399,579), root:(399,608),
    state 0x1, keycode 21 (keysym 0x2b, plus), same_screen YES,
    XLookupString gives 1 bytes: (2b) "+"
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 5845735, (399,579), root:(399,608),
    state 0x1, keycode 50 (keysym 0xffe5, Caps_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

@antoine-gallix
Copy link
Author

update, I tried unchecking all the layout options in the GUI, and revert to the most vanilla us standard keyboard. Then proceed to activate the extend option, and this alone produces the bug above. This should rule out any complicated iteraction of layout and option as source of the problem.

@antoine-gallix
Copy link
Author

Any suggestion on how I could proceed to debug this issue? The extend file looks fine, nothing special in the definition of the = key. Yet this option alone on top of the most basic us keyboard layout produces the error above.

@DreymaR
Copy link
Owner

DreymaR commented Nov 30, 2021

As you say, there's nothing strange about the Extend entry for the equals key (key ) that I can see. If you comment out the lines in that entry alone, the problem appears?

How about if you swap key codes between that line and another that's currently working for you? Could you try that out please?

Bear in mind that to reset the xkb options you should open with an empty option string, like this:
setxkbmap -option "" -option "misc:extend"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants