Re: Bug#351621: xfree86-driver-synaptics: Default configuration inadequate, mouse move way to slowly ...
On Mon, 06 Feb 2006, Mattia Dongili wrote:
> Hello!
Hi !
> Did you read /usr/share/doc/xfree86-driver-synaptics/README.alps and
> tried the configuration suggested there?
>
> The 3rd paragraph says:
> "Since ALPS touchpads don't have the same resolution as Synaptics
> touchpads, you probably have to change some parameter values."
I didn't even know that I have an Alps touchpad until this morning when I
started to dig into /proc and /sys to find out how to identify my
touchpad...
As I said, customizing the MaxSpeed/MinSpeed/AccelFactor helps (I
discovered this by reading the synaptics manual page) so this README
certainly gives a working config.
> It didn't make much sense[1] to rename the package when Xorg entered
> Debian, maybe with the modular X I'll use the same naming scheme as X.
> [1]: http://lists.debian.org/debian-x/2005/06/msg00551.html
Yeah, please follow the convention introduced by the modular Xorg (and
having the same source package in Debian and Ubuntu certainly helps in
many areas since many tools rely on this, like the various scripts
used by Utnubu to compare Debian and Ubuntu)
> Oh, actually it seems they are affected by this same bug(?) but never
> reported here (who knows about upstream...).
> https://launchpad.net/distros/ubuntu/dapper/+source/xserver-xorg-input-synaptics/+bugs
Indeed !
I CC fabbione that he can explain what Ubuntu has decided to do for this
bug.
> Anyway they obviously have different priorities than we have so maybe
> shipping an older version of the driver is better than trying to fix
> regressions.
That's the kind of decision they are forced to make given the man
power/delay problem they encounter from time to time.
However I'm interested to fix the regression in Debian ! :-)
> README.alps is pretty clear about the problem being a different
> resolution on different touchpad models (Synaptics v/s ALPS) so either
> one needs a specific configuration.
> Can you try the suggested ALPS configuration in README.alps? If that
> works the bug can be closed (IMO).
IMO it can't ... the driver should auto-detect the kind of Touchpad and
adjust the default values of the resolution stuff so that it works out of
the box on *any* hardware.
If upstream doesn't want that (and I could understand that since I don't
know any portable way to auto-detect hardware), then we need to
auto-install a different configuration when the Debian package detects
Alps touchpad.
> Did you experienced any different behaviour with older versions of the
> debian package?
I have the laptop since December only so I can't say ...
> BTW: I'm wondering why Ubuntu's package is supposed to work "out of the
> box" but I don't know what Ubuntu sets up ([gk]synaptics?) and I'm not
> really worried about that as their "{up,down}grade dance" seems much
> more dangerous (looking at the bugs they're suffering that are actually
> fixed in the latest version) than working with upstream to fix current
> bugs and/or regressions.
> <fiddling with Ubuntu's launchpad>
> Oh, it seems they automated the process in the xserver configuration
> scripts.
>
> Back to Debian's: currently no setup is done in my package. Probably the
> modular dexconf will allow a better integration of external drivers in
> xorg.conf and the touchpad can be automagically configured upon
> installation. Let's see.
Okay, ccing debian-x to have feedback on this aspect. We certainly need to
have a way to properly configure a touchpad so that it works "out of the
box".
Cheers,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
Reply to: