Binary package hint: xserver-xorg-input-synaptics
On maverick the eePC synaptics touchpad does not work the right way. Tapping does not work and the touchpad is illogically mapped 1:1 to the screen.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1024x600
edid-base64: AP///////wAGryAQAAAAAAESAQOAEwt4CvpWklZUmCQaT1QAAAABAQEBAQEBAQEBAQEBAQEBsBMAQEFYGSAYiAMBw3EAAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBBMDg5U1cwMSBWMCAKABk=
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
Date: Mon Sep 6 11:52:32 2010
DkmsStatus: virtualbox-ose, 3.2.8: added
GdmLog:
Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: GNOME_SUDO_PASSSorry, try again.
sudo: 3 incorrect password attempts
MachineType: ASUSTeK Computer INC. 901
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-19-generic root=UUID=77c08795-d48b-477a-9365-5a8aa506a961 ro quiet splash
ProcEnviron:
LANG=fi_FI.utf8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 10/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1703
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1703:bd10/14/2008:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-19-generic
Hi latrom,
Thanks for reporting the bug and help us to make ubuntu better. The description you provided does not clearly states your problem. Could you please be more elaborate the bug description.