Open WLCIssuesBot opened 7 years ago
Comment by johalun
Tuesday Jan 10, 2017 at 06:39 GMT
Cleaner log:
01/09/17 22:37:09 - [main.c:43] [wlc] SIGUSR2
01/09/17 22:37:09 - [main.c:43] [wlc] wlc_set_active 1
01/09/17 22:37:09 - [main.c:43] [wlc] udev.c activate_event: active 1
01/09/17 22:37:09 - [main.c:43] [wlc] libinput: resume
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_open /dev/input/event0
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_OPEN
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c fd_open: Open path /dev/input/event0. Stored fd 4 to index 0
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_open /dev/input/event1
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_OPEN
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c fd_open: Open path /dev/input/event1. Stored fd 6 to index 1
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_close 20
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_CLOSE
01/09/17 22:37:09 - [main.c:43] [wlc] Close index 0, fd 4
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_open /dev/input/event2
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_OPEN
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c fd_open: Open path /dev/input/event2. Stored fd 4 to index 0
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_close 20
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_CLOSE
01/09/17 22:37:09 - [main.c:43] [wlc] Close index 1, fd 6
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_open /dev/input/event3
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_OPEN
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c fd_open: Open path /dev/input/event3. Stored fd 6 to index 1
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_close 20
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_CLOSE
01/09/17 22:37:09 - [main.c:43] [wlc] Close index 0, fd 4
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_open /dev/input/event4
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_OPEN
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c fd_open: Open path /dev/input/event4. Stored fd 4 to index 0
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c wlc_fd_close 20
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: FD_CLOSE
01/09/17 22:37:09 - 01/09/17 22:37:09 - [main.c:43] [main.c:43] [wlc] fd.c wlc_fd_activate[wlc] Close index 1, fd 6
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request
01/09/17 22:37:09 - [main.c:43] [wlc] fd.c handle_request: TYPE_ACTIVATE
01/09/17 22:37:09 - [main.c:43] [wlc] Activate: Iterate fd 0, value 4
01/09/17 22:37:09 - [main.c:43] [wlc] Activate: FD_INPUT
01/09/17 22:37:09 - [main.c:43] [wlc] Activate: Iterate fd 1, value -1
01/09/17 22:37:09 - [main.c:43] [wlc] Activate: Iterate fd 2, value -1
01/09/17 22:37:09 - [main.c:43] [wlc] Activate: Iterate fd 3, value -1
01/09/17 22:37:09 - [main.c:43] [wlc] Activate: Iterate fd 4, value -1
01/09/17 22:37:09 - [main.c:43] [wlc] Activate: Iterate fd 5, value 10
01/09/17 22:37:09 - [main.c:43] [wlc] Activate: FD_DRM
01/09/17 22:37:09 - [main.c:43] [wlc] Set drm master
Comment by Cloudef
Tuesday Jan 10, 2017 at 09:44 GMT
I've seen this in rare cases so there is probably race condition somewhere. Whole tty switching is flaky.
Comment by johalun
Tuesday Jan 10, 2017 at 17:23 GMT
Some more debugging gave me this output: [wlc] opening input device '/dev/input/event0' failed (Operation not permitted)
That would explain why they're closed again after opened.
Have anyone seen anything similar on Linux?
After resume (vt switch back) libinput_resume is called and /dev/input/event[0-4] is being re-opened as expected but each device is immediately closed again except for the last one which is neither kb or mouse so I lose input methods...
(sorry for the excessive udev output...)
log snippet from when switching back to vt9 where Sway is running.
fd 1,2,3,4 should contain input devices (they do before vt switch). As can be seen in the log, for some reason FD_CLOSE requests are coming in and closing the input devices....
Until doing vt switch Sway works fine with all input devices.