Keyd.service is running but keyboard doesn't work
I have a basic config, pasted below, and i use a redragon keyboard plugged into a Dell computer. When i first start the computer, the redragon keyboard doesn't work. The notebook keyboard works, albeit not respecting the config defined by the keyd.service. If i restart the notebook, both keyboards works fine. If i wait about 1 minute, the redragon keyboard starts working.
[ids]
*
[main]
### MAIN LAYER
#Disable F4
f4 = noop
#Maps capslock to escape when pressed and control when held
capslock = overload(control, esc)
#Remaps the escape key to capslock
esc = capslock
#Makes shift, meta, control and alt oneshot so you dont have to hold
shift = oneshot(shift)
meta = oneshot(meta)
control = oneshot(control)
leftalt = oneshot(alt)
rightalt = oneshot(altgr)
This is the output from journactl -u keyd.service
mar 20 21:39:39 schuler systemd[1]: Started key remapping daemon.
mar 20 21:39:39 schuler keyd[3611]: CONFIG: parsing /etc/keyd/default.conf
mar 20 21:39:39 schuler keyd[3611]: Starting keyd v2.5.0 ()
mar 20 21:39:39 schuler keyd[3611]: DEVICE: ignoring 0fac:1ade:d2b36ae6 (keyd virtual pointer)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: ignoring 1fd2:5001:c0d1e981 (Melfas LGD AIT Touch Controller Mouse)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: ignoring 1fd2:5001:7cc83d56 (Melfas LGD AIT Touch Controller)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: match 0000:0000:afb86503 /etc/keyd/default.conf (Dell WMI hotkeys)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: ignoring 06cb:7621:24fb2daf (DLLA70A:00 06CB:7621 Touchpad)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: ignoring 06cb:7621:28ba9c41 (DLLA70A:00 06CB:7621 Mouse)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: match 0000:0006:bdb72f48 /etc/keyd/default.conf (Video Bus)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: match 0000:0006:bdb72f48 /etc/keyd/default.conf (Video Bus)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: ignoring 258a:002a:b436ff8e (SINO WEALTH Gaming KB Mouse)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: match 258a:002a:9e13b65a /etc/keyd/default.conf (SINO WEALTH Gaming KB Keyboard)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: match 258a:002a:000c7ead /etc/keyd/default.conf (SINO WEALTH Gaming KB Consumer Control)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: match 258a:002a:75e84400 /etc/keyd/default.conf (SINO WEALTH Gaming KB )
mar 20 21:39:39 schuler keyd[3611]: DEVICE: match 04d9:fc30:dac2317f /etc/keyd/default.conf (USB Gaming Mouse Consumer Control)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: match 04d9:fc30:a95d6a08 /etc/keyd/default.conf (USB Gaming Mouse)
mar 20 21:39:39 schuler keyd[3611]: DEVICE: ignoring 04d9:fc30:8afad8f8 (USB Gaming Mouse)
mar 20 21:40:16 schuler keyd[3611]: DEVICE: match 0001:0001:a31694d4 /etc/keyd/default.conf (AT Translated Set 2 keyboard)
Why do you want to wait until after 0.9.0 with those, do you intend to release soon?
Use SIG_IGN for SIGCHLD instead of our own handler https://github.com/swaywm/sway/commit/8238e5242bdbbc4c3b7cba0651c620a89b872a27
I think that would break pipemenus and prompts (once implemented).
- Use wl_event_loop_add_signal for exit signals swaywm/sway@8f089f0
I think we are already doing that, there should be no traditional signal handler within labwc.
Why do you want to wait until after
0.9.0with those, do you intend to release soon?
I'm pondering releasing 0.9.0 after a cool-down as a stake in the ground, but don't feel strongly. Shall we discuss on IRC?
i've been testing https://github.com/swaywm/sway/commit/05e895c4638293a6bfe594ff0cae4eaab63b740e with the wlroots-19 patch for a couple days now. verbatim copy/paste into server.c. result: +80 fps in Arma3 main menu (gtx 1650 - nvidia's driver)
wlroots-18
wlroots-19 + drm sync
i've been testing swaywm/sway@05e895c with the wlroots-19 patch for a couple days now. verbatim copy/paste into server.c. result: +80 fps in Arma3 main menu (gtx 1650 - nvidia's driver)
went through the gauntlet of all the steam games i have installed and have not spotted any regressions.
Nice, feel free to open a PR with your changes.
tearing control https://github.com/swaywm/sway/commit/9a1c411abd8261c121dcd50dfe54132718768084
We already support this protocol, don't we?
tearing control swaywm/sway@9a1c411
We already support this protocol, don't we?
Oh, yes. Good catch.