GNOME Bugzilla – Bug 766264
Unable to enable touchpad with keyboard
Last modified: 2016-05-11 12:52:41 UTC
If one accidentally clicks on the button to disable the touchpad then you cannot enable it with the keyboard as it never gets focused. Pressing tab just cycles the focus between the widgets in the panels above the touchpad panel. This makes it rather hard to enable the touchpad again as one has to use gsettings or dconf-editor.
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 766186 ***
Hmm, by the way, it should not be possible to disable touchpad if mouse/touchscreen isn't connected: https://git.gnome.org/browse/gnome-control-center/tree/panels/mouse/gnome-mouse-properties.c#n129 Isn't this feature corrupted somehow?
(In reply to Ondrej Holy from comment #2) > Hmm, by the way, it should not be possible to disable touchpad if > mouse/touchscreen isn't connected: > https://git.gnome.org/browse/gnome-control-center/tree/panels/mouse/gnome- > mouse-properties.c#n129 > > Isn't this feature corrupted somehow? If you're not meant to be able to disable the only pointing device then it looks like there's a bug somewhere - there are no other pointing devices connected to the laptop although xinput lists several slave pointer devices: $xinput --list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Broadcom Corp id=10 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Video Bus id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ Broadcom Corp id=9 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ Dell WMI hotkeys id=13 [slave keyboard (3)]