-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange trackpad behaviour after wakeup from suspend (not hibernate/shutdown) #7090
Comments
I have the same issue using a Dell XPS 15. It's rarer for me, and for me the trackpad does not get back to normal. I will post a debug log here the next time I see it. |
It can take a good while before it goes back to normal. Sometimes maybe 10-15 minutes. |
Something else interesting to check: if you run |
I have this problem too but it happens with my bluetooth mouse as well as trackpad. |
I have this problem too but it happens with my bluetooth mouse as well as trackpad.
(suspend)
|
I noticed that even if I quit sway, and load it back up, it remains like this. I had to reboot to get this to go away. Has anyone else experienced that or is that unique to me? |
I noticed that even if I quit sway, and load it back up, it remains like this. I had to reboot to get this to go away. Has anyone else experienced that or is that unique to me? I also tested it where I booted, did not start sway/wayland (no display manager), suspended, and came back. I then started sway, and sure enough I have to click twice on everything. |
There'a a bug reported in libinput upstream that matches your description: https://gitlab.freedesktop.org/libinput/libinput/-/issues/712 The upstream bug describes the same problem happening in Gnome, so I guess it's unlikely to be a Sway bug? |
That bug seems to describe a problem with the touch part of the touch pad, but moving the mouse cursor works perfectly fine in my situation. Mouse clicks are what are impacted for me. But I'll check it out. |
I also have the same issue and haven't been able to properly debug it yet. A workaround that
|
Same issue here, my workaround is a bit simpler:
then my touchpad works again. |
I just had the same behavior with gnome, maybe this is not related to sway at all... |
Same behavior for me, on Fedora 38 + Sway : after resuming from suspect, touchpad requires 3 fingers for scroll (until I read this issue, I hadn't realized using 3 fingers instead of 2 would work). Something that I realized is that the identifier of the touchpad changes when the weird behaviour happens: When the touchpad requires 3 fingers, it is recognized as a SynPS/2 Synaptics TouchPad: $ swaymsg -t get_inputs | jq '.[] | select(.type=="touchpad")'
{
"identifier": "2:7:SynPS/2_Synaptics_TouchPad",
"name": "SynPS/2 Synaptics TouchPad",
"vendor": 2,
"product": 7,
"type": "touchpad",
"scroll_factor": 1.0,
"libinput": {
"send_events": "enabled",
"tap": "disabled",
"tap_button_map": "lrm",
"tap_drag": "enabled",
"tap_drag_lock": "disabled",
"accel_speed": 0.0,
"accel_profile": "adaptive",
"natural_scroll": "disabled",
"left_handed": "disabled",
"click_method": "button_areas",
"middle_emulation": "disabled",
"scroll_method": "two_finger",
"dwt": "enabled",
"dwtp": "enabled"
}
} While when it works correctly (e.g.: after reboots, usually), it's being seen as a "Synaptics TM2749-001": $ jq '.[] | select(.type=="touchpad")' < input-touchpad-working.json
{
"identifier": "1739:0:Synaptics_TM2749-001",
"name": "Synaptics TM2749-001",
"vendor": 1739,
"product": 0,
"type": "touchpad",
"scroll_factor": 1.0,
"libinput": {
"send_events": "enabled",
"tap": "disabled",
"tap_button_map": "lrm",
"tap_drag": "enabled",
"tap_drag_lock": "disabled",
"accel_speed": 0.0,
"accel_profile": "adaptive",
"natural_scroll": "disabled",
"left_handed": "disabled",
"click_method": "button_areas",
"middle_emulation": "disabled",
"scroll_method": "two_finger",
"dwt": "enabled",
"dwtp": "enabled"
}
} This seems to be consistent |
Sway Version: 1.7 Archlinux
Debug Log: still working on catching that
Configuration File:
Description:
This does not happen with any non-wayland wm/de and I haven't tried another wlroots/non-wlroots compositor.
My Laptop is a Xiaomi Notebook Pro 2018 with
I'm still trying to catch this happening in a debug log but if there's any more info I can supply in the meantime let me know.
The text was updated successfully, but these errors were encountered: