[Maverick] Touchpad has started acting odd (absolute position?)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-synaptics (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xserver-
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-
ProcVersionSign
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/////
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=
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_GB.UTF-8
SourcePackage: xserver-
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.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Equium A100
dmi.product.
dmi.sys.vendor: TOSHIBA
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-15-generic
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