Hi Pascal,

Since it seems to all be working for me, I hesitate to mess with it.

I still have two issues, neither of which are too serious (or else maybe 
I still dont understand them).

1) The touch pad, under synaptic, is supposed to scroll when you touch 
it with two fingers. With your previous changes, the synaptic driver has 
been removed, as verified by /var/log/system, (as intended), so the 
two-finger scroll is not working at all. But the touch pad does respond 
to the one finger (thumb) touch, and works just like a second mouse input.

2) Every now and then, as I'm typing, my thumb slightly touches the 
touchpad causing the focus to move to
where-ever the mouse pointer is sitting at that moment (i.e., some 
random position). Once my thumb, or more likely
my palm, touches the track pad, anything I'm typiing moves to the 
pointer (mouse) random location, so my typing
focus moves away from where the cursor is. Note I'm distinguishing the 
typing location (cursor) from the mouse pointer location, as they are 
distinct pointers.

Having the text-cursor (pointer at which your typing) switch to the 
mouse pointer (pointer that moves with the mouse) location, while your 
typing, is a very serious problem, as you typing moves to that location.

"Bandaid workaround"
So my workaround, and it is quite effective is to place two large 
bandaids on the left and right side of the touchpad,
to mask off about 1 inch on each side.  Once I did this, the touch pad 
became useful again. It is simply too large,
so large, that I cannot avoid touching it as I type. Note, I'm a full 10 
finger typer, not a two finger "pecker."

For a small move of the mouse pointer, I can use the trackpad via thumb. 
For large movements, that's too inefficient, so I use the red 
eraser-head (track point mouse).

The orginal problem was that the mouse would randomly stick on. That 
problem has been gone since I implemented your #49 posting at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817

For reference:

$ :/var/log$ grep psmouse dmesg
[    3.195521] psmouse serio1: synaptics: queried max coordinates: x 
[..5472], y [..4448]
[    3.276710] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, 
id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00/0x0, board id: 1611, fw 
id: 774180
[    3.276720] psmouse serio1: synaptics: serio: Synaptics pass-through 
port at isa0060/serio1/input0
[    4.070928] psmouse serio2: trackpoint: IBM TrackPoint firmware: 
0x0e, buttons: 3/3

Another thought:

what would happen if we simply deleted/rename the synaptic driver
module?

locate touchscreen|grep synaptics
/usr/src/linux-headers-3.16.0-67-generic/include/config/touchscreen/synaptics

/lib/modules/3.16.0-67-generic/kernel/drivers/input/mouse/synaptics_i2c.ko
/lib/modules/3.16.0-67-generic/kernel/drivers/input/mouse/synaptics_usb.ko
/lib/modules/3.16.0-67-generic/kernel/drivers/staging/ste_rmi4/synaptics_i2c_rmi4.ko

lsmod|grep synaptic
  nothing returned
lsmod|grep psmouse
  psmouse               131072  0

Jont

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1506817

Title:
  left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have reported the details of this problem at
  https://answers.launchpad.net/ubuntu-certification/+question/272142

  As summarized on that question:

  X250 analysis:
   I used the command on the X250
    evtest /dev/input/event15 | grep EV_KEY

   I can see the bug, as follows:

  I click on button 1 (left) over and over. When I push the button down,
  I see it register as 1,
  and when I let go of the key, it registers as a 0.

  The bug is that every now and then (once every 20 clicks), when I let go
  of the left mouse button (BIN_LEFT), it does not return to state 0 (it stays 
in state 1).

  This is highly random, but cant be triggered more often, by dragging a
  window, which I do with BIN_LEFT.

  I am using a brand new X250, purchased in late July 2015. The system was 
returned 3 times to IBM repair as I assumed
  this was a hardware error. Now with the above, it seems clear that this is a 
software issue.

  Ubuntu 15.04

  apt-cache policy xserver-xorg-input-synaptics
  xserver-xorg-input-synaptics:
    Installed: 1.8.1-1ubuntu1
    Candidate: 1.8.1-1ubuntu1
    Version table:
   *** 1.8.1-1ubuntu1 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 16 04:52:03 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  InstallationDate: Installed on 2015-08-15 (61 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CMCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=5718b40f-944e-47a3-acda-04e29336d0bc ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET36W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Oct 16 03:31:10 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id                                1079 
   vendor                                     LGD
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to