On 05/23/2018 09:00 PM, David C. Rankin wrote:
On 05/23/2018 07:21 PM, ken wrote:
Not a mouse. It's a touchpad... although to be perfectly clear :) ...
# hwinfo --mouse 39: PS/2 00.0: 10500 PS/2 Mouse [Created at input.249] Unique ID: AH6Q.Y_f5kDtfqz2 Hardware Class: mouse Model: "SynPS/2 Synaptics TouchPad" Vendor: 0x0002 Device: 0x0007 "SynPS/2 Synaptics TouchPad" Compatible to: int 0x0210 0x0001 Device File: /dev/input/mice (/dev/input/mouse0) Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event4, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse Device Number: char 13:63 (char 13:32) Driver Info #0: Buttons: 1 Wheels: 0 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=new, avail=yes, need=no, active=unknown
For current libinput use, see: https://wiki.archlinux.org/index.php/Libinput
e.g. $ xinput list-props 'SynPS/2 Synaptics TouchPad'
For synaptics see: https://wiki.archlinux.org/index.php/Touchpad_Synaptics
e.g. $ synclient -l
(you may very well have both available on 42.3 - I do)
Both pages will explain how to look at the current configuration and how to adjust the configuration to your liking.
Those are all very interesting webpages and commands. Thanks. Unfortunately though, I didn't see anything there, including when listing properties using "xinput" and "synclient", which was relevant, or even suggestive of being relevant, to NaturalScrolling or scrolling of any kind. The first webpage you point out talks about using a command called "libinput"; other webpages I read mentioned that as well, but my system, though it has libraries containing that name, doesn't have any executable by that name. Nor do either "zypper se libinput" or "yum search libinput" show any package which I don't already have installed. So for a few reasons, all of that seems like a dead-end. Moreover, those tools (xinput and synclient) and others like them, while they can be used to set many of a touchpad's properties, any changes made using them, would probably be wiped out upon the next reboot... perhaps even sooner (by systemd?). While they would be useful for developers, they're too low on the "executable chain" to be useful in resolving my issue. Looking in the logs, I found mention of "XINPUT" and "TouchPad" in /var/log/Xorg.0.log ... but unfortunately that file doesn't timestamp anything, so I can't correlate anything there with any other event, particular with my last reboot when this issue (and others) first appeared. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org