Hello. Laptop - asus x541s. Axis - ubuntu server 16.10. Window manager (window manager, if so correct) - i3wm. Keyboard vinga connected to the laptop through the hub. Configured xkb as follows - created a ~/.config/xkbconf with the following config:

 xkb_keymap { xkb_keycodes { # мСняСм ΠΊΠ½ΠΎΠΏΠΊΠΈ мСстами include "evdev+aliases(qwerty)" #<LCTL> = 37; #<CAPS> = 66; #<LWIN> = 133; <LCTL> = 66; <CAPS> = 133; <LWIN> = 37; }; xkb_types { include "complete" }; xkb_compat { # Π·Π°ΠΆΠΈΠ³Π°Π΅ΠΌ scroll lock ΠΏΡ€ΠΈ русской раскладкС include "complete" include "ledscroll(group_lock)" }; xkb_symbols { include "pc+us+ru(ruu):2+inet(evdev)+capslock(grouplock)" }; xkb_geometry { include "pc(pc105)" };

};

and when loading xkbcomp .config/xkbconf $DISPLAY execute the xkbcomp .config/xkbconf $DISPLAY . Everything is working. But periodically the settings flies to the "default" (caps again becomes caps, control, etc.). The failure pattern cannot be followed in any way. xkbcomp .config/xkbconf $DISPLAY command xkbcomp .config/xkbconf $DISPLAY on the key combination win-f1. Pressing the combination immediately corrects the situation, but failure sometimes occurs at the time of typing, which delivers wildly. Any idea what the problem is and how to solve it?

  • why on server X? and the settings may go off if there is some kind of failure (exception). Tried to update the driver? - Senior Pomidor
  • @SeniorAutomator, this is a home laptop. I installed Ubuntu Server because i3wm is interested in the window manager. There were no drivers for the clave. Google for firewood is also silent - alvoro
  • Without firewood, your clave would not work. Look for the latest drivers for your keyboard on the Internet, update and see. but check. what version is new. Your default driver is in the system - Senior Pomidor
  • That's all that Google can find on my clave)) Drivers are not even close - alvoro
  • see point 2 of this answer . - aleksandr barakin

0