[Debian-eeepc-devel] Bug#666946: Bug#666946: eeepc-acpi-scripts: Please use xinput instead of synclient to handle touchpad

recoverym4n at gmail.com recoverym4n at gmail.com
Tue Apr 3 17:23:01 UTC 2012


On Tue, Apr 03, 2012 at 06:33:33AM -0300, Ben Armstrong wrote:
> Could you also please provide any kernel messages relating to your device?

Sure. An interesting thing, though: according to /var/log/Xorg.0.log, the
touchpad reports itself as 'FSPPS/2 Sentelic FingerSensingPad'.
According to /var/log/messages, udev finds this touchpad as

Mar 27 00:28:50 x101h kernel: [    6.324293] input: FSPPS/2 Sentelic FingerSensingPad as /devices/platform/i8042/serio1/input/input9

I've attached a relevant part of /var/log/messages and Xorg.0.log to this
letter, just in case.

><skip>
> 
> The counter-argument is "well, I don't run GNOME and therefore my WM
> or desktop environment doesn't handle this". Well, in that case I
> would say you should file a bug on your WM to have it do the right
> thing.

Well, I don't use GNOME DE indeed, although I have nothing against it.
As long as DE provides me a way to run a good terminal emulator - it is
a good DE in my book. If default configuration of such DE provides me
letters of sensible size - it is excellent DE. Both GNOME2 and GNOME3
behave OK on first part, and fail badly on second. Nothing that a bit of
configuration couldn't fix, though.

I agree with you that current approach of detecting an X display is
fragile at best. Still, it is unknown to me whenever GNOME (or some other
DE or WM) have means to enable or disable input devices. If this fine
package takes 'offload this and that to DE' approach - then it probably
needs to be documented somehow what exact keypresses DE needs to react for.






More information about the Debian-eeepc-devel mailing list