GNOME Bugzilla – Bug 617932
enable/disable trackpoint or dualpointstick
Last modified: 2019-03-20 10:52:26 UTC
In my laptop I have a secondary mouse device (ALPS) which is a dual point stick. Since I never use it I would like to have a checkbox to disable it. I can disable the device using xinput, so this thing should be possible in gnome-control-center too
Could you show us the output of "xinput list --long" for the device in question? Is it the touchpad, or another device that presents itself as a touchpad? If you have 2 actual separate pointing devices that show themselves as touchpads, I'm afraid that GNOME will not cater for that, and will only allow you to disable/enable "touchpads" as a class, not single input devices. So you might be better off call xinput to disable your device from a startup script.
*** Bug 590258 has been marked as a duplicate of this bug. ***
Hello Bastien. I executed the command that you wrote and this is the output. I think the first is the touchpad, and the second is the stick: ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=12 [slave pointer (2)] Reporting 3 classes: Class originated from: 12 Buttons supported: 12 Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down Button Horiz Wheel Left Button Horiz Wheel Right None None None None None Button state: Class originated from: 12 Detail for Valuator 0: Label: Rel X Range: 0.000000 - 1023.000000 Resolution: 0 units/m Mode: relative Class originated from: 12 Detail for Valuator 1: Label: Rel Y Range: 0.000000 - 767.000000 Resolution: 0 units/m Mode: relative ⎜ ↳ DualPoint Stick id=11 [slave pointer (2)] This device is disabled Reporting 3 classes: Class originated from: 11 Buttons supported: 5 Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down Button state: Class originated from: 11 Detail for Valuator 0: Label: Rel X Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 1: Label: Rel Y Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative
As per comment 2, I'm afraid that we won't cater for that.
I'm sorry but I didn't understand how could you say that the point stick is presents itself as a touchpad. Where do I have to look at?
*** Bug 658980 has been marked as a duplicate of this bug. ***
The duped screen is about disabling the touchpad when using the trackpoint. So what's really being asked in those 2 bug reports is a way to switch between those 2. That's probably something that could be implemented in gnome-settings-daemon, making the "touchpad toggle" button switch between touchpad and trackpoint/touchpad/trackpoint and back, instead of just enabling/disabling the touchpad. You'll have to rely on somebody else implementing this though, as I don't have any hardware with trackpoints.
An old bug obviously, so apologies for resurrecting but it was linked to from a recent discussion. In this particular case though: what is the use-case for disabling the trackstick. Just because you can? Unlike the touchpad the trackstick usually doesn't generate fake events so leaving it enabled should have few side-effects.
Nicolò, any updates?
Disabling the trackpad is useful because it's in the middle of the keyboard, so it's easy to touch it without wanting. Thanks
hmm, interesting. I find that the amount of pressure I have to exert on the trackstick to move it is well beyond what I'd put onto a key, so even accidental touches don't move the pointer. This may be a hw-specific issue though? For the archives, I filed an RFE for libinput here. https://bugs.freedesktop.org/show_bug.cgi?id=85780 Disabling the trackstick is already possible.
Maybe it's hardware specific, as you say, Anyway if you don't find it's useful, no problem. Before you make the decision to close the issue, just consider that all (windows) drivers has an option to disable the trackpad. Thanks
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/166.