Description of problem: After closing laptop lid and re-opening it touchpad stop's working at all. Although I can use keyboard and touchscreen normally without any problem. Reboot is necessary to make it working again. Version-Release number of selected component (if applicable): 1.7.2-2.fc26 How reproducible: 1. Close laptop lid. 2. Open laptop lid. 3. Touchpad is not working. Actual results: Touchpad is not working. Expected results: Touchpad works. Additional info: My notebook is Lenovo Yoga 3 Pro. I'm running Fedora 26 (Gnome with Wayland session) with all latest updates. I don't know if it's connected with libinput, but in previous Fedora version (25) everything works like a charm.
probably libinput, F26 has a lid switch handling that disables the touchpad when the lid is closed to avoid ghost touches. This should work normally though, unless the lid switch is unreliable (and not marked as such). https://who-t.blogspot.com.au/2017/02/libinput-and-lid-switch-events.html So the first thing to do is: run sudo evemu-record against the lid switch device after resume and attach the output here, I wonder if the state remains as closed. Also run sudo libinput-debug-events --verbose in a terminal and then suspend+resume, that should give us some hint too.
Created attachment 1286318 [details] Evemu record of lid switch 1) run sudo evemu-record 2) Choose lid switch event 3) Close lid 4) Resume noteboook 5) Enter password 6) Enter CTRL+C in console 7) Save console output
Created attachment 1286320 [details] Libinput debug events 1) run sudo libinput-debug-events --verbose 2) Close lid 3) Resume notebook 4) Enter password 5) Use touchpad (doesn't work, no " event14 POINTER_MOTION" in console), keyboard (works) and touchscreen (works) 5) CTRL+C in console 6) Save console output
ok, the lid switch log and the debug log look correct and libinput detects the lid being opened. so let's rule out the last thing: run sudo evemu-record and select the touchpad device, does the kernel device send events after suspend?
I've tested it with evemu, and You are right. After resume kernel device (touchpad selected in evemu-record) doesn't send any events.
Sorry for the delay. Could you attach a dmesg from the boot, containing the suspend resume action in it too?
Created attachment 1291937 [details] Dmesq log from boot, suspend and resume Boot pc, log in, close lid, open lid, touchpad doesn't work anymore.
Thanks for the log. The dmesg shows that this is the exact same issue than bug #1431375, so closing this one as a dup, and continuing to work on that in bug #1431375 *** This bug has been marked as a duplicate of bug 1431375 ***