[hardy] SHMConfig should be on by default

[Alex Wauck]

Binary package hint: xserver-xorg

If I remove or rename my xorg.conf (which we would like to get rid of for Hardy, right?), gsynaptics will not run because SHMConfig is not on. SHMConfig should default to being on for Synaptics touchpads. Also, scrolling does not work on my touchpad without fiddling with xorg.conf. The touchpad in question is an ALPS touchpad (which I understand is a rebranded Synaptics touchpad).

[Alex Wauck (awauck)]

Well, after I read the documentation, it looks like ALPS touchpads aren't quite the same as Synaptics touchpads, and SHMConfig is insecure. Perhaps a separate driver would be better? I'll see if there's a good way to at least make scrolling work by default.

[Alex Wauck (awauck)]

It looks like a bit of HAL magic can fix it. I made X use synaptics by copying /usr/share/doc/hal/examples/10-x11-input.fdi to /etc/hal/fdi/policy and making a slight change because my ALPS touchpad behaves like a touchscreen when evdev handles it.

[Timo Aaltonen (tjaalton)]

So evdev handles your touchpad just fine? What exactly is fixed then?

[Alex Wauck (awauck)]

evdev does not handle my touchpad correctly. Instead, it behaves like a touchscreen. That is, when I tap some place on my touchpad, the cursor will instantly move to the corresponding location on my screen when evdev is being used. When this occurs, the cursor cannot be moved to the top gnome-panel. The synaptics driver has the correct behavior (i.e. tap=click (not move), scrolling by dragging on the right-hand side of the touchpad, etc.).