https://bugs.freedesktop.org/show_bug.cgi?id=106498
--- Comment #5 from Peter Hutterer <[email protected]> ---
Strange, and unfortunately the test devices I have here don't seem to reproduce
this issue.
evdev_device_suspend()
- we expect that to be called with the device (if in doubt, print
evdev_device->devname
evdev_notify_suspended_device()
- this notifies other devices that a device has been suspended so they can
update their state (e.g. suspending a touchpad disables the disable-while-
typing pairing with the keyboard)
tp_interface_device_removed()
- this should not be called because it would imply that the device tries to
notify itself
So the next thing to check here is what the argument is to
evdev_notify_suspended_device() and whether it's the touchpad. If not, then we
probably have some memory corruption somewhere. If it is the touchpad, check
the list_for_each loop and why the 'continue' condition doesn't trigger. That's
likely the explanation.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
