xkb-switch-i3
xkb-switch-i3 copied to clipboard
Zebradil
The program sometimes resets my keyboard auto-repeat settings
I am not entirely sure, but it seems that with this program mentioned in i3's config file, sometimes my keyboard auto delay settings get reset. It is in the file .xinitrc where I set 'xset r rate 250 30'. Sometimes, roughly every 5th time I boot the computer, the keyboard auto delay rate isn't 250:30 but the default: 660:25. This is kinda annoying. When I remove xkb-switch-i3 from the i3's config file, it seems to work just fine.
Hi @donaastor,
I'm not sure if I can help you with this issue.
The difference between xkb-switch-i3 and the original xkb-switch is that the former subscribes to i3 events and invokes xkb-switch function to switch the layout when the window switch event happens.
To debug this issue further, I would suggest disabling xkb-switch-i3 and using xkb-switch for changing the keyboard layout. This might help to figure out if xkb-switch causes the described side effect or if it is something else.
I experienced a somehow similar issue when reconnecting a usb-device resets xkb configuration (the one you can see with setxkbmap -query). I'm not sure it's related, but it shows that some strange things can happen without direct influence from xkb-switch-i3.
Hello @Zebradil,
Thank you for answering and giving me these tips! You are right and I forgot about that, that the issue might be of xkb-switch itself.
Also, before I go out to test it I want to ask you please, is it completely fine to only restart X server, i.e. to go back to TTY and then do startx? Would all bugs be reproduced as if I rebooted the whole machine?
Unfortunately, I can't say for sure, but I would strongly expect that restarting the X server should re-populate all configuration customizations.
After a month of booting up my PC, I can confirm that the problem is gone. I still don't know what was causing it, but it seems that I ensured some synchronization just by delaying starting my programs for about 1.5 and 2.5 seconds after boot. I use this software and another small code that I wrote that also subscribes to X keyboard events... There was probably some interference... Anyway, I believe you can mark this issue as solved