Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: What can I do to make the pointer in the keyboard move easier?

204 views
Skip to first unread message

Boris K.

unread,
Nov 19, 2014, 6:30:55 AM11/19/14
to
On Wed, 19 Nov 2014 06:14:53 -0500, Chris Ahlstrom wrote:

> But, worst come to worst, you can always use xinput:
>
> http://unix.stackexchange.com/questions/90572/how-can-i-set-mouse-sensitivity-not-just-mouse-acceleration

Following directions, I run "xinput list" which reports:
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Integrated Camera id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)]

I don't know if I want device #4 or device #11 above, so, I'll run both:
$ xinput list-props 4
Device 'Virtual core XTEST pointer':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
XTEST Device (257): 1
$ ^4^10
xinput list-props 10
Device 'AT Translated Set 2 keyboard':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Product ID (258): 1, 1
Device Node (259): "/dev/input/event3"

Unfortunately, I don't see the "acceleration" or "deceleration" values that
are described in the reference at
http://unix.stackexchange.com/questions/90572/how-can-i-set-mouse-sensitivity-not-just-mouse-acceleration

Boris K.

unread,
Nov 19, 2014, 6:44:25 AM11/19/14
to
On Wed, 19 Nov 2014 11:39:52 +0000, William Poaster wrote:

> I've no idea why Ubuntu doesn't have synatic installed by default.
> If he *hasn't* got it installed, maybe "apt-get synaptic" would do it

Whatever "synaptic" is, Kubuntu thinks it's already there on the
command line, but Kubuntu thinks it's not there in the System Settings.
$ sudo apt-get install synaptic
Reading package lists... Done
Building dependency tree
Reading state information... Done
synaptic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 168 not upgraded.

There does seem to be a $HOME/.synaptic/synaptic.conf file:

$ cat $HOME/.synaptic/synaptic.conf
Synaptic "" {
ViewMode "0";
showWelcomeDialog "0";
vpanedPos "537";
hpanedPos "200";
windowWidth "809";
windowHeight "761";
windowX "751";
windowY "180";
ToolbarState "2";
Maximized "0";
Install-Recommends "1";
};

But I don't see how that configuration file helps.

Cybe R. Wizard

unread,
Nov 19, 2014, 8:28:52 AM11/19/14
to
On Wed, 19 Nov 2014 05:44:24 -0600
"Boris K." <boriski...@yahoo.com> wrote:

> On Wed, 19 Nov 2014 11:39:52 +0000, William Poaster wrote:
>
> > I've no idea why Ubuntu doesn't have synatic installed by default.
> > If he *hasn't* got it installed, maybe "apt-get synaptic" would do
> > it
>
> Whatever "synaptic" is...

You could pay a little closer attention. What you want and what is
being called for is not, "synaptic," which is a package handler:
----------
"Synaptic is a graphical package management tool based on GTK+ and APT.
Synaptic enables you to install, upgrade and remove software packages in
a user friendly way."
----------

What you really want is, "xserver-xorg-input-synaptics," which
is a touchpad driver:
----------
"This package provides an input driver for the X.Org X server to enable
advanced features of the Synaptics Touchpad including"
----------

Had you actually /used/ synaptic, you could have searched for,
"synaptic," and found what you really really want.

Isn't Linux fun? ;-]

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"

Boris K.

unread,
Nov 19, 2014, 8:52:28 AM11/19/14
to
On Wed, 19 Nov 2014 07:28:35 -0600, Cybe R. Wizard wrote:

> What you really want is, "xserver-xorg-input-synaptics," which
> is a touchpad driver:
> ----------
> "This package provides an input driver for the X.Org X server to enable
> advanced features of the Synaptics Touchpad including"

Thank you for that hint.

It seems to be installed already:
$ sudo apt-get install xserver-xorg-input-synaptics
Reading package lists... Done
Building dependency tree
Reading state information... Done
xserver-xorg-input-synaptics is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 168 not upgraded.

It's not an executable:
$ which xserver-xorg-input-synaptics
Doesn't report anything.

But, it does seem to exist:
$ locate xserver-xorg-input-synaptics
/usr/share/apport/package-hooks/source_xserver-xorg-input-synaptics.py
/usr/share/apport/package-hooks/xserver-xorg-input-synaptics-lts-quantal.py
/usr/share/bug/xserver-xorg-input-synaptics
/usr/share/bug/xserver-xorg-input-synaptics/script
/usr/share/doc/xserver-xorg-input-synaptics
/usr/share/doc/xserver-xorg-input-synaptics/NEWS.Debian.gz
/usr/share/doc/xserver-xorg-input-synaptics/README.Debian
/usr/share/doc/xserver-xorg-input-synaptics/README.alps
/usr/share/doc/xserver-xorg-input-synaptics/README.gz
/usr/share/doc/xserver-xorg-input-synaptics/changelog.Debian.gz
/usr/share/doc/xserver-xorg-input-synaptics/copyright
/usr/share/doc/xserver-xorg-input-synaptics/trouble-shooting.txt.gz
/var/lib/dpkg/info/xserver-xorg-input-synaptics.list
/var/lib/dpkg/info/xserver-xorg-input-synaptics.md5sums

The question is how to run it.
Googling for "how to run xserver-xorg-input-synaptics", it seems to be
related to the touchpad:
https://packages.debian.org/sid/xserver-xorg-input-synaptics

Apparently, this command *should* have worked (but failed):
$ synclient
Couldn't find synaptics properties. No synaptics driver loaded?

Cybe R. Wizard

unread,
Nov 19, 2014, 10:36:31 AM11/19/14
to
On Wed, 19 Nov 2014 07:52:27 -0600
"Boris K." <boriski...@yahoo.com> wrote:

> On Wed, 19 Nov 2014 07:28:35 -0600, Cybe R. Wizard wrote:
>
> > What you really want is, "xserver-xorg-input-synaptics," which
> > is a touchpad driver:
> > ----------
> > "This package provides an input driver for the X.Org X server to
> > enable advanced features of the Synaptics Touchpad including"
>
> Thank you for that hint.
>
> It seems to be installed already:

See this:
<https://help.ubuntu.com/community/SynapticsTouchpad>

Boris K.

unread,
Nov 19, 2014, 1:42:51 PM11/19/14
to
On Wed, 19 Nov 2014 09:52:22 -0600, Johnny wrote:

> Have you looked in the Driver Manager in System Settings?

Based on that suggestion, I went to KDE System Settings, and,
saw, under "System Administration" the "Driver Manager".

http://i57.tinypic.com/w8kpbr.jpg

Going there, it collected information about the system for
a while, but then, all it reported was the following, which
was pretty useless, unfortunately, unless there's something
hidden there that is related to the keyboard pointer.

NVIDIA Corporation GT216GLM [Quadro FX 880M]
( )Using NVIDIA legacy binary driver - version 304.117 from nvidia-304
( )Using NVIDIA legacy binary driver - version 304.117 from nvidia-304-updates
( )Using NVIDIA binary driver - version 331.38 from nvidia-331 (Recommended Driver)
(o)Using NVIDIA binary driver - version 331.38 from nvidia-331-updates
( )Using X.Org X server -- Noveau display driver from xserver-xorg-video-nouveau

That driver manager seems to be *only* for the display driver.
Is there a way to get it to report the pointer drivers?

Boris K.

unread,
Nov 19, 2014, 1:48:23 PM11/19/14
to
On Wed, 19 Nov 2014 09:36:14 -0600, Cybe R. Wizard wrote:

> See this:
> <https://help.ubuntu.com/community/SynapticsTouchpad>

Thanks for that suggestion, as there must be a solution.
My "touchpad" on the Lenovo laptop doesn't work (never did
on Ubuntu). It works on Windows, but not Kubuntu nor Ubuntu.
Never understood why.

Am reading that article to see if it offers a clue.
SynapticsTouchpad

Contents

Introduction
Default clickpad gestures
Basic Configuration with a Graphical Interface
Disabling Touchpad while Typing
Completely disabling Touchpad
Adjust Touchpad Sensitivity
Troubleshooting
Determine whether a touchpad has been detected
Enabling SHMConfig in order to get synclient debug output
Touchpad not working after login
Control touchpad features using synclient
See also
Known Issues

Introduction

A touchpad, and clickpad is a built-in input device for laptops that is used as a computer mouse. Synaptics is a driver for these.

Default clickpad gestures

The default gestures are:

Single finger press on the top 80% of the clickpad surface = primary click
Two finger press on the top 80% of the clickpad surface = secondary click
Two finger movement vertically = scroll vertically
Two finger movement horizontally = scroll horizontally

When clicking the bottom 20% clickpad buttons, one would want to use two fingers to maximize the accuracy of the click.

Basic Configuration with a Graphical Interface

Ubuntu provides basic configuration of your touchpad options in System > Preferences > Mouse, under the Touchpad tab.

Try the touchpad after unchecking the Enable mouse clicks with touchpad check box.

Check operation after Enable horizontal scrolling is checked. This may not have been the default setting.

Disabling Touchpad while Typing

Go to System > Preferences > Mouse > Touchpad and uncheck 'Disable touchpad while typing' and 'Enable mouse clicks with touchpad'. (This method is not available under Ubuntu 14.04.)

Completely disabling Touchpad

Some systems don't have the option to permanently disable the touchpad via BIOS or it's located in an external keyboard. To fully disable you can do the following:

Determine the device id (the device name should be something with touchpad or glidepoint)

xinput list

Disable it (e.g. here the device id is 15)

xinput set-prop 15 "Device Enabled" 0

You may run the command during session startup

Adjust Touchpad Sensitivity

Determine device number (see above)

xinput list

Open a separate terminal to watch emitted events:

Replace [device number] with the number of your touchpad from 'xinput list'. It will probably be one of the devices under "Virtual core pointer".

This step is not mandatory but it can help to track problems:

xinput --test [device number]

If text flies by as you move your mouse pointer using the touchpad, you know that you got the correct device number.

Open another terminal to see current settings: (Again this step can be omitted but is helpful to see available options. Watch for "Synaptics Finger". It will change as soon as you apply the next command.)

xinput --watch-props [device number]

Set sensitivity:

xinput --set-prop [device number] "Synaptics Finger" 50 80 257

The terminal running 'xinput --watch-props' should now display

Property 'Synaptics Finger' changed.
Synaptics Finger (267): 50, 80, 257

The higher you set the numbers the more force is needed to make an event fire. And the less sensitive the touchpad get.

Troubleshooting

Determine whether a touchpad has been detected

To check if a touchpad has been detected open a terminal and check the input device list given by this command:

xinput list

If one of the lines mentions a touchpad or glidepoint (perhaps also "Synaptics" or "ALPS"), your touchpad has been detected.

If one of the lines mentions an "ADB mouse", then your touchpad is old. Use the trackpad command line tool to configure it. Here's an example to switch on tapping and dragging:

sudo trackpad show
sudo trackpad tap
sudo trackpad drag

Enabling SHMConfig in order to get synclient debug output

Online, the most commonly found procedure for doing this involves using HAL. However, since HAL hasn't been present in Ubuntu since 10.04, you will have to do it the other way -- by editing xorg.conf.

sudo gedit /etc/X11/xorg.conf

Paste this into the document:

Section "InputClass"
Identifier "enable synaptics SHMConfig"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "SHMConfig" "on"
EndSection

If it's not empty, put it at the end. Save, close the file and reboot.

Now you should be able to see what kind of input your touchpad detects by running

synclient -m 100

The synclient manpage will explain what the numbers you see onscreen mean.

Touchpad not working after login

This usually happens when you disable your touchpad and then suspend your computer. To fix this just run this command:

gconftool-2 --set --type boolean /desktop/gnome/peripherals/touchpad/touchpad_enabled true

If nothing else works, please see the official Ubuntu touchpad debugging article.

Control touchpad features using synclient

synclient is a commandline utility to query and modify Synaptics driver options. This would allow one to adjust touchpad features that may not be exposed via the GUI. One would adjust parameters via a terminal:

synclient PARAMETER=#

where PARAMETER is as listed below, and # is a number. While the formal definition of each parameter may be found in the synaptics manpage, here is a more user friendly description of each of the parameters:

LeftEdge

RightEdge

TopEdge

BottomEdge

FingerLow

FingerHigh

MaxTapTime

MaxTapMove

MaxDoubleTapTime

SingleTapTimeout

ClickTime

EmulateMidButtonTime

EmulateTwoFingerMinZ

EmulateTwoFingerMinW

VertScrollDelta - Controls the speed and direction of vertical scrolling. The fastest natural direction scroll speed is 1. Larger positive values decrease the scroll speed. The fastest reverse direction scroll speed is -1, with larger negative values decreasing the scroll speed.

HorizScrollDelta - Controls the speed and direction of horizontal scrolling. The fastest natural direction scroll speed is 1. Larger positive values decrease the scroll speed. The fastest reverse direction scroll speed is -1, with larger negative values decrease the scroll speed.

VertEdgeScroll - Enables=1/Disables=0 vertical scrolling when dragging across the right edge of the touchpad.

HorizEdgeScroll - Enables=1/Disables=0 vertical scrolling when dragging across the right edge of the touchpad.

CornerCoasting

VertTwoFingerScroll - Enables=1/Disables=0 vertical scrolling when using two fingers anywhere on the touchpad.

HorizTwoFingerScroll - Enables=1/Disables=0 horizontal scrolling when using two fingers anywhere on the touchpad.

MinSpeed - Adjusts the minimum speed of your touchpad cursor. Lowest is 0.

MaxSpeed - Adjusts the maximum speed of your touchpad cursor. Lowest is 0.

AccelFactor - Adjust the rate of speed increment at which the touchpad cursor increases from MinSpeed to MaxSpeed. Lowest is 0.

TouchpadOff - Enables=1/Disables=0 the touchpad entirely.

LockedDrags

LockedDragTimeout

RTCornerButton - Disables=0 click when one taps the right top corner of the touchpad.

RBCornerButton - Disables=0 click when one taps the right bottom corner of the touchpad.

LTCornerButton - Disables=0 click when one taps the left top corner of the touchpad.

LBCornerButton - Disables=0 click when one taps the left bottom corner of the touchpad.

TapButton1

TapButton2

TapButton3

ClickFinger1

ClickFinger2

ClickFinger3

CircularScrolling

CircScrollDelta

CircScrollTrigger

PalmDetect

PalmMinWidth

PalmMinZ

CoastingSpeed

CoastingFriction

PressureMotionMinZ

PressureMotionMaxZ

PressureMotionMinFactor

PressureMotionMaxFactor

ResolutionDetect

GrabEventDevice

TapAndDragGesture

AreaLeftEdge

AreaRightEdge

AreaTopEdge

AreaBottomEdge

HorizHysteresis

VertHysteresis

ClickPad

See also

Turning Synaptics Touchpads On/Off with a Shortcut Key

Known Issues

Tapping top right of touchpad pastes undesirably

Johnny

unread,
Nov 19, 2014, 2:16:10 PM11/19/14
to
On Wed, 19 Nov 2014 12:42:49 -0600
"Boris K." <boriski...@yahoo.com> wrote:

> That driver manager seems to be *only* for the display driver.
> Is there a way to get it to report the pointer drivers?


You can find out if it's installed.


This is from askubuntu.com

If the touchpad is detected correctly, the synaptics driver shold be
autoloaded. Check it with the following command:

cat /var/log/Xorg.0.log | grep -i synaptics

http://askubuntu.com/questions/337049/how-can-i-install-a-synaptics-pointing-driver

Boris K.

unread,
Nov 19, 2014, 2:41:59 PM11/19/14
to
On Wed, 19 Nov 2014 09:36:14 -0600, Cybe R. Wizard wrote:

> See this:
> <https://help.ubuntu.com/community/SynapticsTouchpad>

That site suggested the following, but I couldn't find it in
KDE: "System > Preferences > Mouse, under the Touchpad tab".

But, it also suggested the following command:
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Integrated Camera id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)]

$ xinput --test 11
$ xinput --test 11

motion a[0]=300
motion a[1]=689
motion a[1]=688
motion a[0]=299 a[1]=686
motion a[0]=296 a[1]=680
motion a[0]=293 a[1]=672
motion a[0]=289 a[1]=661
motion a[0]=286 a[1]=651
motion a[0]=282 a[1]=635
motion a[0]=276 a[1]=619
motion a[0]=272 a[1]=606
motion a[0]=268 a[1]=595
motion a[0]=265 a[1]=587
motion a[0]=263 a[1]=578
motion a[0]=261 a[1]=571
motion a[0]=260 a[1]=570
......

I'm not sure what that shows, but it certainly shows the
trackball working as I moved it, the numbers grew.

I was also able to disable and enable the trackball at will:
$ xinput set-prop 11 "Device Enabled" 0
$ xinput set-prop 11 "Device Enabled" 1

I was able to look at its properties:
$ xinput --watch-props 11
Device 'TPPS/2 IBM TrackPoint':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (262): 0
Device Accel Constant Deceleration (263): 1.000000
Device Accel Adaptive Deceleration (264): 1.000000
Device Accel Velocity Scaling (265): 10.000000
Device Product ID (258): 2, 10
Device Node (259): "/dev/input/event5"
Evdev Axis Inversion (266): 0, 0
Evdev Axes Swap (268): 0
Axis Labels (269): "Rel X" (152), "Rel Y" (153)
Button Labels (270): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151)
Evdev Middle Button Emulation (271): 1
Evdev Middle Button Timeout (272): 50
Evdev Third Button Emulation (273): 0
Evdev Third Button Emulation Timeout (274): 1000
Evdev Third Button Emulation Button (275): 3
Evdev Third Button Emulation Threshold (276): 20
Evdev Wheel Emulation (277): 1
Evdev Wheel Emulation Axes (278): 6, 7, 4, 5
Evdev Wheel Emulation Inertia (279): 10
Evdev Wheel Emulation Timeout (280): 200
Evdev Wheel Emulation Button (281): 2
Evdev Drag Lock Buttons (282): 0

Unfortunately, the web page says to look for "Device Finger", and
to set "Synaptics Finger", but that doesn't seem to exist, so I'm
not sure what to change to speed up the trackball.

$ xinput --set-prop 11 "Synaptics Finger" 50 80 257
property 'Synaptics Finger' doesn't exist, you need to specify its type and format

So, I think this is close but I just need to figure out the
sensitivity setting command.

Boris K.

unread,
Nov 19, 2014, 3:02:06 PM11/19/14
to
On Wed, 19 Nov 2014 13:41:57 -0600, Boris K. wrote:

> So, I think this is close but I just need to figure out the
> sensitivity setting command.

Thanks to caver1, I "think" I'm getting closer!
https://help.ubuntu.com/community/SynapticsTouchpad

This web page was really for the trackpad (which I have, but, which
doesn't work and never did).

But, I was able to determine the trackball is device 11, and
I was able to spit out the characteristics of device 11.

One of those, seems to be the acceleration of the mouse, which
wasn't what I was looking for, but it's close.

I changed that acceleration from "10" ...
$ xinput --set-prop 11 "Device Accel Velocity Scaling" 10
To 100 ...
$ xinput --set-prop 11 "Device Accel Velocity Scaling" 100
And the trackball then moved really fast. Too fast. But, at
least that affected the trackball, so, all I need to do now
is figure out what settings affect the ease of pushing it.

Boris K.

unread,
Nov 19, 2014, 3:03:14 PM11/19/14
to
On Wed, 19 Nov 2014 13:16:09 -0600, Johnny wrote:

> cat /var/log/Xorg.0.log | grep -i synaptics

It's not found, unfortunately.
Yet, apt-get says it's installed.
Dunno why.

Boris K.

unread,
Nov 19, 2014, 3:05:51 PM11/19/14
to
On Wed, 19 Nov 2014 14:02:05 -0600, Boris K. wrote:

> Thanks to caver1, I "think" I'm getting closer!
> https://help.ubuntu.com/community/SynapticsTouchpad

I'm clearly getting closer and closer thanks to some experiments
suggested by the reference Caver1 supplied.

This makes the trackball (device #11) move too slowly:
$ xinput --set-prop 11 "Device Accel Velocity Scaling" 10

This makes the trackball move way too fast:
$ xinput --set-prop 11 "Device Accel Velocity Scaling" 100

This seems like a good compromise:
$ xinput --set-prop 11 "Device Accel Velocity Scaling" 50

The movement of the trackball seems complicated because it
overshoots, so, I probably need to set some more things
before it works the way it should; but this is a good start!

Boris K.

unread,
Nov 19, 2014, 3:18:34 PM11/19/14
to
On Wed, 19 Nov 2014 09:36:14 -0600, Cybe R. Wizard wrote:

> See this:
> <https://help.ubuntu.com/community/SynapticsTouchpad>

Ooops. Cybe R. Wizard was the one who suggested this site,
which seems to have the answers, if I keep experimenting.

This tells me all the properties I can change:
$ xinput --watch-props 11
Device 'TPPS/2 IBM TrackPoint':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (262): 0
Device Accel Constant Deceleration (263): 1.000000
Device Accel Adaptive Deceleration (264): 1.000000
Device Accel Velocity Scaling (265): 50.000000
Device Product ID (258): 2, 10
Device Node (259): "/dev/input/event5"
Evdev Axis Inversion (266): 0, 0
Evdev Axes Swap (268): 0
Axis Labels (269): "Rel X" (152), "Rel Y" (153)
Button Labels (270): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151)
Evdev Middle Button Emulation (271): 1
Evdev Middle Button Timeout (272): 50
Evdev Third Button Emulation (273): 0
Evdev Third Button Emulation Timeout (274): 1000
Evdev Third Button Emulation Button (275): 3
Evdev Third Button Emulation Threshold (276): 20
Evdev Wheel Emulation (277): 1
Evdev Wheel Emulation Axes (278): 6, 7, 4, 5
Evdev Wheel Emulation Inertia (279): 10
Evdev Wheel Emulation Timeout (280): 200
Evdev Wheel Emulation Button (281): 2
Evdev Drag Lock Buttons (282): 0

This made the trackpoint dog slow!
$ xinput --set-prop 11 "Device Accel Constant Deceleration" 10
So, the default value of "1" seems better:
xinput --set-prop 11 "Device Accel Constant Deceleration" 1

Changing this seems to slow down the deceleration of the trackpoint:
$ xinput --set-prop 11 "Device Accel Adaptive Deceleration" 10

The nice thing is that I can keep a log of the changes in
another window ...
xinput --watch-props 11
Device 'TPPS/2 IBM TrackPoint':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (262): 0
Device Accel Constant Deceleration (263): 1.000000
Device Accel Adaptive Deceleration (264): 1.000000
Device Accel Velocity Scaling (265): 10.000000
Device Product ID (258): 2, 10
Device Node (259): "/dev/input/event5"
Evdev Axis Inversion (266): 0, 0
Evdev Axes Swap (268): 0
Axis Labels (269): "Rel X" (152), "Rel Y" (153)
Button Labels (270): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Left" (150), "Button Horiz Wheel Right" (151)
Evdev Middle Button Emulation (271): 1
Evdev Middle Button Timeout (272): 50
Evdev Third Button Emulation (273): 0
Evdev Third Button Emulation Timeout (274): 1000
Evdev Third Button Emulation Button (275): 3
Evdev Third Button Emulation Threshold (276): 20
Evdev Wheel Emulation (277): 1
Evdev Wheel Emulation Axes (278): 6, 7, 4, 5
Evdev Wheel Emulation Inertia (279): 10
Evdev Wheel Emulation Timeout (280): 200
Evdev Wheel Emulation Button (281): 2
Evdev Drag Lock Buttons (282): 0
Property 'Device Accel Velocity Scaling' changed.
Device Accel Velocity Scaling (265): 40.000000
Property 'Device Accel Velocity Scaling' changed.
Device Accel Velocity Scaling (265): 10.000000
Property 'Device Accel Velocity Scaling' changed.
Device Accel Velocity Scaling (265): 100.000000
Property 'Device Accel Velocity Scaling' changed.
Device Accel Velocity Scaling (265): 50.000000
Property 'Device Accel Constant Deceleration' changed.
Device Accel Constant Deceleration (263): 10.000000
Property 'Device Accel Constant Deceleration' changed.
Device Accel Constant Deceleration (263): 1.000000
Property 'Device Accel Constant Deceleration' changed.
Device Accel Constant Deceleration (263): 2.000000
Property 'Device Accel Constant Deceleration' changed.
Device Accel Constant Deceleration (263): 1.000000
Property 'Device Accel Adaptive Deceleration' changed.
Device Accel Adaptive Deceleration (264): 10.000000

Boris K.

unread,
Nov 19, 2014, 3:19:22 PM11/19/14
to
On Wed, 19 Nov 2014 14:05:50 -0600, Boris K. wrote:

>> https://help.ubuntu.com/community/SynapticsTouchpad
>
> I'm clearly getting closer and closer thanks to some experiments
> suggested by the reference Caver1 supplied.

Ooops. Cybe Wizard supplied it.

Cybe R. Wizard

unread,
Nov 19, 2014, 3:29:47 PM11/19/14
to
SHHH! Don't tell the kops!

Boris K.

unread,
Nov 19, 2014, 3:50:03 PM11/19/14
to
On Wed, 19 Nov 2014 14:29:25 -0600, Cybe R. Wizard wrote:

> SHHH! Don't tell the kops!

Thanks Cybe R. Wizard for that expert help, as it was the only suggestion
that worked, to date. I much appreciate the advice.

The settings didn't survive a reboot, so, I just now put this in
my .bash_aliases file:
$ xinput --set-prop 11 "Device Accel Velocity Scaling" 50
$ xinput --set-prop 11 "Device Accel Adaptive Deceleration" 10

I'm curious about what those of you who have that little red
trackpoint on the Lenovo machines, what settings you have?

This tells me that my trackpoint is device 11:
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Integrated Camera id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)]

This tells me what my trackpoint properties are currently set to:
$ xinput -list-props 11
Device 'TPPS/2 IBM TrackPoint':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (262): 0
Device Accel Constant Deceleration (263): 1.000000
Device Accel Adaptive Deceleration (264): 10.000000
Device Accel Velocity Scaling (265): 50.000000
Device Product ID (258): 2, 10
Device Node (259): "/dev/input/event5"
Evdev Axis Inversion (266): 0, 0
Evdev Axes Swap (268): 0
Axis Labels (269): "Rel X" (152), "Rel Y" (153)
Button Labels (270): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151)
Evdev Middle Button Emulation (271): 1
Evdev Middle Button Timeout (272): 50
Evdev Third Button Emulation (273): 0
Evdev Third Button Emulation Timeout (274): 1000
Evdev Third Button Emulation Button (275): 3
Evdev Third Button Emulation Threshold (276): 20
Evdev Wheel Emulation (277): 1
Evdev Wheel Emulation Axes (278): 6, 7, 4, 5
Evdev Wheel Emulation Inertia (279): 10
Evdev Wheel Emulation Timeout (280): 200
Evdev Wheel Emulation Button (281): 2
Evdev Drag Lock Buttons (282): 0

And, this, of course, changes them:
$ xinput --set-prop 11 "Device Accel Velocity Scaling" 50
$ xinput --set-prop 11 "Device Accel Adaptive Deceleration" 10

William Unruh

unread,
Nov 19, 2014, 4:29:58 PM11/19/14
to
On 2014-11-19, Boris K. <boriski...@yahoo.com> wrote:
> On Wed, 19 Nov 2014 14:29:25 -0600, Cybe R. Wizard wrote:
>
>> SHHH! Don't tell the kops!
>
> Thanks Cybe R. Wizard for that expert help, as it was the only suggestion
> that worked, to date. I much appreciate the advice.
>
> The settings didn't survive a reboot, so, I just now put this in
> my .bash_aliases file:
> $ xinput --set-prop 11 "Device Accel Velocity Scaling" 50
> $ xinput --set-prop 11 "Device Accel Adaptive Deceleration" 10

You could try using /etc/X11/xorg.conf or in /etc/X11/xorg.conf.d to put in those settings, and
then it should survive reboot.

Sorry I cannot tell you exactly how to do it however.

Boris K.

unread,
Nov 19, 2014, 4:35:31 PM11/19/14
to
On Wed, 19 Nov 2014 21:29:44 +0000, William Unruh wrote:

> You could try using /etc/X11/xorg.conf or in /etc/X11/xorg.conf.d to put in those settings, and
> then it should survive reboot.
>
> Sorry I cannot tell you exactly how to do it however.

The bash aliases seems to have worked.
It doesn't work in the very beginning, but, it kicks in the
moment I open up a terminal window.

So, I'm OK now, although the cursor still overshoots, so,
I need to figure out the damping figure.

Jonathan N. Little

unread,
Nov 19, 2014, 5:54:50 PM11/19/14
to
Boris K. wrote:
> On Wed, 19 Nov 2014 13:16:09 -0600, Johnny wrote:
>
>> cat /var/log/Xorg.0.log | grep -i synaptics
>

Useless use of cat ;-)

grep -i synaptics /var/log/Xorg.0.log

> It's not found, unfortunately.
> Yet, apt-get says it's installed.
> Dunno why.

Sure it is installed?

dpkg -l |grep synaptic

Is it loading?

synclient -l


Don't know which version Lenovo or Ubuntu you are using but with the
template in :

/usr/share/X11/xorg.conf.d/50-synaptics.conf

copy to :

/etc/X11/xorg.conf.d

You could try an tweak referencing this thread might get you going.

<http://ubuntuforums.org/showthread.php?t=1941819>

I haven't come across a touchpad yet that didn't work OOTB, but I have
been installing the main flavor and haven't used KDE since Mandrake 10.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Boris K.

unread,
Nov 19, 2014, 6:41:49 PM11/19/14
to
On Wed, 19 Nov 2014 17:54:56 -0500, Jonathan N. Little wrote:

> grep -i synaptics /var/log/Xorg.0.log

$ grep -i synaptics /var/log/Xorg.0.log
Didn't report anything.

> dpkg -l |grep synaptic

$ dpkg -l |grep synaptic
ii synaptic 0.81.1ubuntu1 amd64 Graphical package manager
ii xserver-xorg-input-synaptics 1.7.4-0ubuntu1 amd64 Synaptics TouchPad driver for X.Org server

> synclient -l

$ synclient -l
Couldn't find synaptics properties. No synaptics driver loaded?

> Don't know which version Lenovo or Ubuntu you are using
> but with the template in :

It's 14.04 Kubuntu on top of Ubuntu.

Chris Ahlstrom

unread,
Nov 19, 2014, 7:26:31 PM11/19/14
to
William Unruh wrote this copyrighted missive and expects royalties:
These days you can add a snippet of an xorg.conf to a file stored in
/etc/X11/xorg.d, rather than having to construct a whole xorg.conf that must
specify all settings, even those that are discovered properly by Xorg.

(There is a command to generate an xorg.conf based on what gets probed:
"Xorg -configure" as root, I believe. Verified.)

--
QOTD:
"It wouldn't have been anything, even if it were gonna be a thing."

Chris Ahlstrom

unread,
Nov 19, 2014, 7:29:28 PM11/19/14
to
Boris K. wrote this copyrighted missive and expects royalties:

> On Wed, 19 Nov 2014 21:29:44 +0000, William Unruh wrote:
>
>> You could try using /etc/X11/xorg.conf or in /etc/X11/xorg.conf.d to put in those settings, and
>> then it should survive reboot.
>>
>> Sorry I cannot tell you exactly how to do it however.
>
> The bash aliases seems to have worked.
> It doesn't work in the very beginning, but, it kicks in the
> moment I open up a terminal window.

You can usually set up your desktop environment to run a startup script
containing your tweaks. For example, in XFce, add it via Applications /
Settings / Session and Startup.

> So, I'm OK now, although the cursor still overshoots, so,
> I need to figure out the damping figure.

Good progress, and you've learned some nice tidbits along the way!

--
If researchers wrote nursery rhymes...

Little Miss Muffet sat on her gluteal region,
Eating components of soured milk.
On at least one occasion,
along came an arachnid and sat down beside her,
Or at least in her vicinity,
And caused her to feel an overwhelming, but not paralyzing, fear,
Which motivated the patient to leave the area rather quickly.
-- Ann Melugin Williams

jeff g.

unread,
Nov 19, 2014, 9:23:15 PM11/19/14
to
In his case, he is using nVidia proprietary driver so it would be better
for him to use the xorg.conf created by nVidia.

--
Jeff G.

In the front yard of a funeral home: 'Drive carefully. We'll wait.'

Cybe R. Wizard

unread,
Nov 19, 2014, 9:48:02 PM11/19/14
to
On Wed, 19 Nov 2014 19:26:28 -0500
Chris Ahlstrom <OFee...@teleworm.us> wrote:

> These days you can add a snippet of an xorg.conf to a file stored in
> /etc/X11/xorg.d, rather than having to construct a whole xorg.conf
> that must specify all settings, even those that are discovered
> properly by Xorg.

Oh! Good info, thanks loads.
>
> (There is a command to generate an xorg.conf based on what gets
> probed: "Xorg -configure" as root, I believe. Verified.)

Knew about that, but the other thing, w00t!

Cybe R. Wizard -learning, learning at 63...

Chris Ahlstrom

unread,
Nov 20, 2014, 6:07:46 AM11/20/14
to
Cybe R. Wizard wrote this copyrighted missive and expects royalties:

> On Wed, 19 Nov 2014 19:26:28 -0500
> Chris Ahlstrom <OFee...@teleworm.us> wrote:
>
>> These days you can add a snippet of an xorg.conf to a file stored in
>> /etc/X11/xorg.d, rather than having to construct a whole xorg.conf
>> that must specify all settings, even those that are discovered
>> properly by Xorg.
>
> Oh! Good info, thanks loads.
>>
>> (There is a command to generate an xorg.conf based on what gets
>> probed: "Xorg -configure" as root, I believe. Verified.)
>
> Knew about that, but the other thing, w00t!

Hmmmm, no such directory on my Debian Sid boxes. It does exist on my CentOS
box.

--
FORTUNE PROVIDES QUESTIONS FOR THE GREAT ANSWERS: #21
A: Dr. Livingston I. Presume.
Q: What's Dr. Presume's full name?

Chris Ahlstrom

unread,
Nov 20, 2014, 6:12:37 AM11/20/14
to
Chris Ahlstrom wrote this copyrighted missive and expects royalties:

> Cybe R. Wizard wrote this copyrighted missive and expects royalties:
>
>> On Wed, 19 Nov 2014 19:26:28 -0500
>> Chris Ahlstrom <OFee...@teleworm.us> wrote:
>>
>>> These days you can add a snippet of an xorg.conf to a file stored in
>>> /etc/X11/xorg.d, rather than having to construct a whole xorg.conf
>>> that must specify all settings, even those that are discovered
>>> properly by Xorg.
>>
>> Oh! Good info, thanks loads.
>>>
>>> (There is a command to generate an xorg.conf based on what gets
>>> probed: "Xorg -configure" as root, I believe. Verified.)
>>
>> Knew about that, but the other thing, w00t!
>
> Hmmmm, no such directory on my Debian Sid boxes. It does exist on my CentOS
> box.

But "man xorg.conf" does verify what I noted, as well as describe a metric
assload of Xorg options..

--
Not one hundred percent efficient, of course ... but nothing ever is.
-- Kirk, "Metamorphosis", stardate 3219.8

Boris K.

unread,
Nov 20, 2014, 12:36:56 PM11/20/14
to
Thanks to everyone, and especially to Cybe R. Wizard for
this reference, the slow-trackpoint problem has been solved!
https://help.ubuntu.com/community/SynapticsTouchpad

Here's my update after a few days of using the fix & rebooting:

FINAL FIX:
I put the following lines in my $HOME/.bash_aliases file:
xinput --set-prop 11 "Device Accel Velocity Scaling" 85
xinput --set-prop 11 "Device Accel Adaptive Deceleration" 10

Note: I couldn't get them both to work on the same line.

FINAL PROCESS:
I found that the trackpoint was device 11 using this command:
$ xinput list
I then listed all the properties of device 11 (trackpoint):
$ xinput -list-props 11

Note: I would have used Xorg suggestions but I couldn't get
the syntax right, so, since it was working, I left it in the
bash_aliases file.
0 new messages