[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#559233: xserver-xorg-input-synaptics: Tap and Scrolling disabled by default on touchpad (and missing documentation to enable it)



On 02-12-2009 22:33, Julien Cristau wrote:
On Wed, Dec  2, 2009 at 21:39:32 -0200, Renato S. Yamane wrote:
The "tap" and "scrolling" is disabled by default and don't exist
documentation explaing how to enabled it.  I hear that it is a choice
from mainstream.

Debian Team can change this, enabling by default.

   * Tapping has been disabled by default on many touchpads by upstream, see
     the "NOTES" section in the synaptics(4) manpage for a short overview
     about how defaults are calculated.
     If you want to re-enable it, you can do so from within the X
     environment by running the following commands in a terminal:

         $ synclient TapButton1=1
         $ synclient TapButton2=2
         $ synclient TapButton3=3

But, think as an domestic user, like your mum:
- Mother: Son, the touchpad is not working.
- Son: Oh Mun, you need go to terminal and type some commands
- Mother: Uhmmmm, now it's working.

After reboot:
- Mother: Hey son, the touchpad is not working again!
- Son: It's happening because the configuration cannot be permanently modified. You need change the xorg.conf or custom FDI file.

WTF!

     Note that the configuration will not be permanently modified, to do
     so assign the above option values in your xorg.conf or custom fdi file
     (see the synaptics(4) manpage

Synaptics manpage don't tell me HOW/WHAT/WHERE can I change it permanently.
This is obscure.

	or the documents in
     /usr/share/doc/xserver-xorg-input-synaptics for additional details).

And none documents tell me HOW can I change it permanently, or how/what I need change on xorg.conf

Closing.  This is documented and we're not going to diverge from
upstream.

The documents on /usr/share/doc/xserver-xorg-input-synaptics (and synaptics manpage) tell us that tap is not enabled by default. Some documents tell that is necessary change somethings on xorg.conf, but it not explain HOW.



Reply to: