https://bugs.freedesktop.org/show_bug.cgi?id=102959
--- Comment #2 from Paviluf <[email protected]> ---
(In reply to Peter Hutterer from comment #1)
> libinput doesn't do anything with suspend, the only thing it does is that it
> disables the touchpad when a lid switch event is received. see
> http://who-t.blogspot.com/2017/02/libinput-and-lid-switch-events.html for an
> explanation.
Suspend is triggered (by systemd it seem) because libinput detect a lid event
in the first place, right ?
> If you hardware is broken, you can set
> LIBINPUT_ATTR_LID_SWITCH_RELIABILITY=write_open
> in the hwdb (have a look at 90-libinput-model-quirks.hwdb, there are entries
> for this already). If that is set, libinput will send a lid open event as
> soon as you start typing. That at least papers over the firmware bug you're
> seeing.
The thing is I strongly doubt that my lid is broken. It's just a possibility.
Since it never happen before I installed Fedora 26, and it happen with 2
different firmware, I'm more inclined to think it's a software problem.
> What does evemu-record on the device show in this case? Does it show an open
> + close event?
It will be hard to know since it only happened once in 10 days since I test the
John Lewis firmware.
--
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
