New comment by kennylevinsen on void-packages repository

https://github.com/void-linux/void-packages/issues/27132#issuecomment-744348052

Comment:
If you drop back to the kernel console but do not have working keyboard input, then it would seem that elogind is not resetting the kernel keyboard mode (with KDSKBMODE) back to K_UNICODE. It is supposed to do this when the session control is either explicitly or implicitly dropped.

What version of elogind was tested against? You could use `busctl monitor` to get a dbus trace and compare with libseat to bare wlroots logind backend.