Input stops working after VT switch back to Sway

[jbeich]

Environment:

• FreeBSD 13.0-CURRENT amd64, drm-current-kmod-4.20.g20190110
• sway version 1.0-rc1-33-gec5da0ca (2019-02-07, branch master)
• wlroots version 0.3-11-g20d404a0 (2019-02-06, branch master)
• libevdev-1.5.9, libinput-1.12.6
• kern.evdev.rcpt_mask=12 (EVDEV_RCPT_HW_MOUSE + EVDEV_RCPT_HW_KBD)
• empty config (i.e., -c /dev/null)
• debug log

Steps to reproduce:

1. Start Sway on DRM (e.g., env -u DISPLAY sway)
2. VT switch to console (e.g., Ctrl + Alt + F1)
3. VT switch back to Sway (e.g., Ctrl + Alt + F2)

Expected result:

• Sway resumes. Everything works like before VT switch.

Actual result:

• Screen is restored, including ongoing animation from applications
• Mouse pointer doesn't move
• Keyboard input has no effect, including Ctrl + Alt + F1
• VT can only be force-switched via vidcontrol -s 1 </dev/ttyv0 (remotely or timed via script)

[emersion]

Hmm, maybe an issue with the wlroots direct session.

[sghctoma]

I've disappeared from here some time ago (life/work got in the way), but a @freebsd-x11 thread (https://lists.freebsd.org/pipermail/freebsd-x11/2019-October/024139.html) made me aware of this issue.
This is not an issue with wlroots/sway, but with libepoll-shim (See jiixyj/epoll-shim#7). VT switching works on my 13.0-CURRENT HardenedBSD system with the latest version from jiixyj's repo.

[emersion]

Thanks for the heads-up. @jbeich can you confirm?

[jbeich]

Yes. After upgrading epoll-shim (via freebsd/freebsd-ports@a7c3fd3d428e) switching to console and back works fine (tried more than once).