[kwin] [Bug 384702] KWin doesn't expose a way to use one keymap per keyboard
https://bugs.kde.org/show_bug.cgi?id=384702 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384702] KWin doesn't expose a way to use one keymap per keyboard
https://bugs.kde.org/show_bug.cgi?id=384702 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384702] KWin doesn't expose a way to use one keymap per keyboard
https://bugs.kde.org/show_bug.cgi?id=384702 aeris changed: What|Removed |Added CC||ae...@imirhil.fr --- Comment #3 from aeris --- Hello, I bump this bug after 5 years, because I'm hitting it on KDE 5 Wayland. Same here, I'm using FR-BEPO layout for my main keyboard (Moonlander), but have a secondary Typematrix keyboard and I need to use US for Yubikey (physically hardcoded to send US keycode). So my X11 config is: ``` Section "InputClass" Identifier "default" MatchIsKeyboard "yes" Option "XkbModel""pc105" Option "XkbLayout" "fr" Option "XkbVariant" "bepo" Option "XkbOptions" "kpdl:kposs,grp:sclk_toggle,compose:lwin" EndSection Section "InputClass" Identifier "typematrix" MatchIsKeyboard "yes" MatchVendor "TypeMatrix.com" Option "XkbModel" "tm2030USB-102" Option "XkbLayout" "fr" Option "XkbVariant" "bepo" Option "XkbOptions" "kpdl:kposs,grp:sclk_toggle,compose:lwin" EndSection Section "InputClass" Identifier "moonlander" MatchIsKeyboard "yes" MatchVendor "ZSA" Option "XkbModel" "pc105" Option "XkbLayout" "fr" Option "XkbVariant" "bepo" EndSection Section "InputClass" Identifier "yubikey" MatchIsKeyboard "yes" MatchVendor "Yubico" Option "XkbModel" "pc105" Option "XkbLayout" "us" Option "XkbVariant" "basic" EndSection ``` Currently Wayland is broken because only one layout is possible, and so I can't have the correct keyboard model (tm2030USB-102 / pc105) or layout (FR-BEPO / US / FR) based on the related physical keyboard. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384702] KWin doesn't expose a way to use one keymap per keyboard
https://bugs.kde.org/show_bug.cgi?id=384702 --- Comment #2 from Pierre Ducroquet--- An udev rule would work, I just thought it would be nice to be able to configure that using the GUI only… FYI, under X11, I configure it manually with xinput/setxkbmap that way : ~$ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=15 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)] ⎜ ↳ Kensington Kensington Expert Mouse id=9[slave pointer (2)] ⎜ ↳ TypeMatrix.com USB Keyboard id=10 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ Integrated Camera id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ ThinkPad Extra Buttonsid=17 [slave keyboard (3)] ↳ Yubico Yubikey 4 OTP+U2F+CCID id=18 [slave keyboard (3)] ↳ TypeMatrix.com USB Keyboard id=11 [slave keyboard (3)] ↳ TypeMatrix.com USB Keyboard id=12 [slave keyboard (3)] ~$ setxkbmap -device 11 fr bepo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384702] KWin doesn't expose a way to use one keymap per keyboard
https://bugs.kde.org/show_bug.cgi?id=384702 Martin Flöserchanged: What|Removed |Added Severity|normal |wishlist Flags||Wayland+, X11- --- Comment #1 from Martin Flöser --- I wasn't aware that such a feature in X existed. It sounds interesting. I don't have a real idea yet how to implement it, but it's certainly something which could be done. Basically all that's needed is to switch the layout to the one specified whenever the keyboard is used. The problem is how to do this specifying. Personally I would prefer if that would be a hint through udev. -- You are receiving this mail because: You are watching all bug changes.