Open PatrickDaG opened 1 year ago
I think that'd be an issue with xkb and not hyprland?
The same settings worked without issue when using X11. Is there a difference when using xkb under X11 as opposed to wayland?
Hm. Odd. What does hyprctl devices
say?
mice:
Mouse at 1beded0:
logitech-g-pro--1
default speed: 0.000000
Mouse at 1cc7870:
kingston-hyperx-alloy-fps-mechanical-gaming-keyboard-mouse
default speed: 0.000000
Mouse at 1f658c0:
kingston-hyperx-alloy-fps-mechanical-gaming-keyboard-consumer-control-1
default speed: 0.000000
Mouse at 1b9df10:
syna329a:00-06cb:cd4f-mouse
default speed: 0.000000
Mouse at 43ac560:
syna329a:00-06cb:cd4f-touchpad
default speed: 0.000000
Keyboards:
Keyboard at 1c65810:
video-bus
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 1e1a9f0:
video-bus-1
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 1ddbec0:
power-button
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 4309a70:
logitech-g-pro-
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 4308ed0:
kingston-hyperx-alloy-fps-mechanical-gaming-keyboard
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 1f18a30:
kingston-hyperx-alloy-fps-mechanical-gaming-keyboard-system-control
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 1e45150:
kingston-hyperx-alloy-fps-mechanical-gaming-keyboard-consumer-control
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 1c7e780:
kingston-hyperx-alloy-fps-mechanical-gaming-keyboard-1
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 1d38fa0:
hp-wide-vision-fhd-camera:-hp-w
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 22210b0:
hp-wide-vision-fhd-camera:-hp-i
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 20b23a0:
intel-hid-events
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 21f1ff0:
intel-hid-5-button-array
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 4455e40:
at-translated-set-2-keyboard
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 4494570:
wireless-hotkeys
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: no
Keyboard at 44d2ea0:
hp-wmi-hotkeys
rules: r "", m "", l "de", v "bone", o ""
active keymap: German (Bone)
main: yes
Tablets:
Tablet at 1b834c0:
elan2514:00-04f3:2817-stylus
Touch:
Touch Device at 1b7c7e0:
elan2514:00-04f3:2817
Touch Device at 1e96520:
elan2514:00-04f3:2817-1
Switches:
Switch Device at 2065a60:
Lid Switch
Switch Device at 43869a0:
Intel HID switches
Switch Device at 1d13400:
HP WMI hotkeys
weird, all your kbs should be in the same keymap. No clue.
I have tested it with sway just now, and it works as intended, the mod keys actually changing layer.
After more trying it seems Mod keys in general are pretty broken. When switching keyboard layouts from my prefered de,bone layout to the standard de,de some Modkeys get mangled up. Such as CapsLock, suddenly having the same effect as right alt. The greater/less and hashtag key, the supposed modkeys under my layout, do not work at all on the external keyboard and internally it work but the key repeat is not applied making it seem there is still something wrong.
mods are governed by xkb
But given that it works without problem both in sway and under X11 I suspect the error lays in Hyprland. I have skimmed the source code of both hyprland and sway and there are differences in how they handle mod keys. Sadly I was not able to find the concrete bug that causes this.
@PatrickDaG
is this resolved
I've just tested it and the problem still remains. Two of the modkeys are not working and do nothing.
I currently have a very similar issue with NEO QWERTZ.
When I set kb_variant
to neo_qwertz
in my config and keep kb_layout
as de
, it seems to have MOD3 (that is "<,>,|" on QWERTZ) inverted. This is putting me on another layer by default. I am in my "normal" home layer when I press that button. I checked this with wev
.
I do not have this issue in, for example, my login shell. The other modkeys seem to be working, but due to the aforementioned issue I cannot say that with 100% certainty.
I'm using hyprland on a laptop with a german keyboard using layout :
This layout includes up to five different layers, being trigger by Mod keys. On the internal keyboard these work as intended, on an external keyboard however two of the modkey do not work correctly The corresponding keycodes from
wev
are: for layer 4:and for layer 3:
wev
returns the same keycodes on the internal keyboard, the only difference is when pressing the mod keys and then pressing another key, on the internal keyboard the correct layer key gets returned, on the external keyboard however the incorrect base layer key gets returned. The corresponding modkeys on the other side, think left_shift/right_shift, functions on both keyboards.The only notable difference between the two keyboard is the internal laptop one has the physical layout of an American keyboard with German key bindings, meaning it is missing a
right shift
key and amenu
key.