After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759745 - Disable touchpad on lid close event
Disable touchpad on lid close event
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: power
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2015-12-21 15:13 UTC by Joao Machado
Modified: 2017-04-22 00:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joao Machado 2015-12-21 15:13:30 UTC
Disable touchpad on lid "close" event and re-enable touchpad on lid event "open".

Issue, is that on laptops that have the "Do not sleep" on lid close or "Automatic Suspend" turned off, and a user closes the lid, touchpads can make the cursor go nuts because of the sensitivity.

Here is a use case, a user is sitting at their desk, needs to move to a conference room, closes the lid and walks 3 minutes to the conference room. Opens the lid and every possible window is opened, open docs modifies accidentally etc. This is because some laptops are very sensitive while others are not. Case in point, we have three Dell XPS14 laptops and two have this issue but the touchpads function perfectly.

My current work around is to use custom keyboard shortcuts to disable and enable the touchpad:

gsettings set org.gnome.desktop.peripherals.touchpad send-events disabled

gsettings set org.gnome.desktop.peripherals.touchpad send-events enable



I believe there should be a switch in the Settings>Mouse&Touchpad>Touchpad to enable/disable the touchpad on lid events open/close.
Comment 1 Bastien Nocera 2015-12-26 23:49:47 UTC
(In reply to Joao Machado from comment #0)
> I believe there should be a switch in the Settings>Mouse&Touchpad>Touchpad
> to enable/disable the touchpad on lid events open/close.

Why would you ever want *not* to do that.

Peter, is this something we can do in libinput, or does it need to happen in higher levels (eg. mutter)?

If the latter, do we have a way to detect whether touchpads are internal to the machine, and only disable the internal touchpads when the lid is closed?

Re-assigning to gnome-settings-daemon for now.
Comment 2 Peter Hutterer 2015-12-28 23:58:19 UTC
I think this would make sense in libinput. For the few devices where the touchpad should be enabled even when the lid is closed (???) we can quirk that in the hwdb.

https://bugs.freedesktop.org/show_bug.cgi?id=93527

(In reply to Bastien Nocera from comment #1)
]> If the latter, do we have a way to detect whether touchpads are internal to
> the machine, and only disable the internal touchpads when the lid is closed?

we don't expose this information atm. If we implemented this, would this be something you want from the libinput API or would you prefer this to be set as a udev property on the device?
Comment 3 Bastien Nocera 2017-04-21 13:10:41 UTC
Fixed in libinput itself, correct?
https://bugs.freedesktop.org/show_bug.cgi?id=92674
Comment 4 Peter Hutterer 2017-04-21 23:57:09 UTC
yep. it's done transparently though so you don't get a notification about the touchpad being disabled. you'll get the notification about the lid switch.
Comment 5 Bastien Nocera 2017-04-22 00:36:17 UTC
Great, nothing more to do on the GNOME side then, thanks!