[Maverick] Touchpad has started acting odd (absolute position?)

Bug #617990 reported by Dave Gilbert
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-input-synaptics

My laptop touchpad has just (after an update on maverick) started acting weird. I think it is working in something
like absolute mode - but not quite; if I tap on the right of the pad it moves quite a way to the right, if I tap on the left it hardly
moves; the further to the right of the pad I tap the further to the right it moves.It doesn't want to move up and down much.

Odd!

Dave

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-input-synaptics 1.2.2-2ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
Architecture: amd64
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800
 edid-base64: AP///////wBMozM2AAAAAAAPAQOAIRV4Cof1lFdPjCcnUFQAAAABAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAQMBMAS88QAAAZAAAADwAAAAAAAAAAACOHAmQCAAAA/gBTQU1TVU5HCiAgICAgAAAA/gBMVE4xNTRYMy1MMDYKAHA=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: Off
 modes: 1024x768 800x600 800x600 848x480 640x480
 edid-base64:
Date: Sat Aug 14 21:55:25 2010
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Equium A100
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=031a90fc-7cc9-4daf-bb3f-4bb3f68653ac ro quiet splash crashkernel=384M-2G:64M,2G-:128M
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
SourcePackage: xserver-xorg-input-synaptics
dmi.bios.date: 10/23/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 2.10
dmi.board.name: MPAD-MSAE Customer Reference Boards
dmi.board.vendor: Intel Corporation
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.10:bd10/23/2006:svnTOSHIBA:pnEquiumA100:pvrPSAABE-00J008EN:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Equium A100
dmi.product.version: PSAABE-00J008EN
dmi.sys.vendor: TOSHIBA
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-15-generic

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

It seems to have fixed itself. Hmm - not sure really what to do ? If it does it again or if anyone else sees it I guess is the question.

Dave

Revision history for this message
Gursimran singh (simar) wrote :

This bug seems to be fixed by itself.

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: New → Invalid
Revision history for this message
Ahmed Shams (ashams) wrote :

just testing it..

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Ahmed Shams (ashams) wrote :

resetting back...

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.