Your message dated Mon, 7 May 2012 19:40:18 +0200
with message-id <[email protected]>
and subject line Re: Bug#381963: serious issues with the touchpad in Latitude
D420
has caused the Debian Bug report #381963,
regarding serious issues with the touchpad in Latitude D420
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
381963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381963
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xserver-xorg-input-synaptics
Version: 0.14.6-1
Severity: important
The Latitude D420 has a touchpad which is detected by the kernel as
follows:
input: PS/2 Mouse as /class/input/input1
input: AlpsPS/2 ALPS GlidePoint as /class/input/input2
The synaptics driver in X.org uses this just fine. However there are two
major issues:
- The sensitivity is way too low. Even when setting it to maximum in
gsynaptics makes it so slow I need something like ten full movements
across the pad just to get the mouse pointer from the middle to the
upper left corner of the screen. I had to multiply the defaults by
ten (giving MinSpeed=0.9 and MaxSpeed=1.8) and manually inject that
into xorg.conf to get what I'd expect as a reasonable default
behaviour from the mouse pointer.
- Tapping and scrolling does not work, even though synclient seems to
indicate that both are enabled. However, there seems to be something
odd going on with the hardware tapping; FWIW, here's a record of me
tapping a few times:
fugl:~> synclient -m 10
time x y z f w l r u d m multi gl gm gr gdx gdy
0.000 518 465 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0
2.038 472 492 40 1 0 0 0 0 0 0 00000000 0 0 0 0 0
2.195 472 492 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0
2.999 525 518 40 1 0 0 0 0 0 0 00000000 0 0 0 0 0
3.155 525 518 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0
3.887 568 431 126 1 0 0 0 0 0 0 00000000 0 0 0 0 0
3.899 565 422 102 1 0 0 0 0 0 0 00000000 0 0 0 0 0
3.947 565 422 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0
and here's the same thing, using the buttons instead:
fugl:~> synclient -m 10
time x y z f w l r u d m multi gl gm gr gdx gdy
0.000 403 365 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0
0.722 403 365 0 0 0 1 0 0 0 0 00000000 0 0 0 0 0
0.854 403 365 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0
1.010 403 365 0 0 0 1 0 0 0 0 00000000 0 0 0 0 0
1.130 403 365 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0
1.286 403 365 0 0 0 1 0 0 0 0 00000000 0 0 0 0 0
1.406 403 365 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0
Given that I use the defaults (except MinSpeed and MaxSpeed),
shouldn't it be able to figure out for itself that I'm tapping, even
though l=0 all the time? (I'm not sure how to debug the vertical
scrolling either; FWIW, x seems to be around 970-1000 when I pull my
finger across the right edge.)
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-sesse
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Versions of packages xserver-xorg-input-synaptics depends on:
ii libc6 2.3.6-18 GNU C Library: Shared libraries
ii libx11-6 2:1.0.0-8 X11 client-side library
ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar
ii libxi6 1:1.0.0-5 X11 Input extension library
ii xserver-xorg-core 1:1.0.2-9 X.Org X server -- core server
xserver-xorg-input-synaptics recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Steinar H. Gunderson <[email protected]> (07/05/2012):
> I've downgraded to squeeze because GNOME 3 drove me nuts, so I'm
> unable to test in unstable. (It's broken in squeeze.)
>
> Anyway, the laptop model is no longer sold, and I'm fine with not
> tapping, so you can probably close.
OK; doing that then.
Thanks for the quick answer.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
