Difference between revisions of "Talk:Touchpad Synaptics"

From ArchWiki
Jump to: navigation, search
(synclient's oddity)
Line 8: Line 8:
  
 
: Just saw your post about this questions in the forums, so it worked.  I had the same problem and found a solution by running "syndaemon -d -K" at start up.  Basically it disables the touchpad on the fly while you are typing, re-enabled automatically after you stop pressing keys.  There are other options to vary the disable time, but I find the default works well.  I can't remember where I found it, forum thread maybe?  Anyway I'd vote for adding a list of things to try to the cursor_jump section of wiki.  Keep the suggestion there now as list item 1, add yours as list item 2, and add the syndaemon as list item 3 one if you want [[User:Ajbibb|Ajbibb]] ([[User talk:Ajbibb|talk]]) 19:52, 21 October 2013 (UTC)
 
: Just saw your post about this questions in the forums, so it worked.  I had the same problem and found a solution by running "syndaemon -d -K" at start up.  Basically it disables the touchpad on the fly while you are typing, re-enabled automatically after you stop pressing keys.  There are other options to vary the disable time, but I find the default works well.  I can't remember where I found it, forum thread maybe?  Anyway I'd vote for adding a list of things to try to the cursor_jump section of wiki.  Keep the suggestion there now as list item 1, add yours as list item 2, and add the syndaemon as list item 3 one if you want [[User:Ajbibb|Ajbibb]] ([[User talk:Ajbibb|talk]]) 19:52, 21 October 2013 (UTC)
 +
 +
==synclient==
 +
To my experience, synclient refuses to change i.e. the parameter RightButtonAreaBottom (by giving a BadValue error) as long as MiddleButtonAreaRight==RightButtonAreaLeft. Not before I adjusted MiddleButton and RightButton to be ''real'' adjacent – by increment RightButtonAreaLeft, synclient accepted changes to RightButtonAreaBottom and MiddleButtonAreaBottom.
 +
 +
In my example I started with
 +
    RightButtonAreaLeft    = 3443
 +
    RightButtonAreaRight    = 0
 +
    RightButtonAreaTop      = 0
 +
    RightButtonAreaBottom  = 3306
 +
    MiddleButtonAreaLeft    = 2636
 +
    MiddleButtonAreaRight  = 3443
 +
    MiddleButtonAreaTop    = 0
 +
    MiddleButtonAreaBottom  = 3306
 +
 +
Trying
 +
$ synclient MiddleButtonAreaBottom=2450
 +
results
 +
X Error of failed request:  BadValue (integer parameter out of range for operation)
 +
  Major opcode of failed request:  131 (XInputExtension)
 +
  Minor opcode of failed request:  37 (X_ChangeDeviceProperty)
 +
  Value in failed request:  0x129
 +
  Serial number of failed request:  22
 +
  Current serial number in output stream:  25
 +
 +
After
 +
$ synclient RightButtonAreaLeft=3444
 +
both
 +
$ synclient MiddleButtonAreaBottom=2450
 +
$ synclient RightButtonAreaBottom=2450
 +
gave no more errors.
 +
 +
As this is, in my opinion, a somewhat surprising behaviour, I'd add a note about this in the synclient-section.
 +
Ok?
 +
-- [[User:Peter0|Peter0]] ([[User talk:Peter0|talk]]) 22:30, 22 June 2014 (UTC)

Revision as of 22:30, 22 June 2014

ALPS touchpads

The article says that kernel 3.3 fixed the detection of ALPS touchpads (among others). I am running kernel 3.6.10 and my ALPS touchpad was not detected until I installed psmouse-alps-driver from the AUR. Therefore I suggest to rewrite the paragraph accordingly to say: "Some touchpads (e.g. ALPS, ...) need additional drivers to work. Install package X for touchpad Y." Any opposing arguments? Markus00000 (talk) 19:12, 15 December 2012 (UTC)

Cursor jump

I have been experiencing an issue where the cursor sometimes starts jumping around the screen when trying to use it (as if its sensitivity is all over the place) I can not recreate it since it's pretty random when it happens so I can not test if the suugested fix at https://wiki.archlinux.org/index.php/Touchpad_Synaptics#Cursor_jump is for that or for another issue. In any case I have found a fix for it by doing 'sudo modprobe -r psmouse; sudo modprobe psmouse' to restart the mouse driver the thing is that I'm not sure whether I should add it to https://wiki.archlinux.org/index.php/Touchpad_Synaptics#Cursor_jump or make a new subheading under https://wiki.archlinux.org/index.php/Touchpad_Synaptics#Troubleshooting ?

Just saw your post about this questions in the forums, so it worked. I had the same problem and found a solution by running "syndaemon -d -K" at start up. Basically it disables the touchpad on the fly while you are typing, re-enabled automatically after you stop pressing keys. There are other options to vary the disable time, but I find the default works well. I can't remember where I found it, forum thread maybe? Anyway I'd vote for adding a list of things to try to the cursor_jump section of wiki. Keep the suggestion there now as list item 1, add yours as list item 2, and add the syndaemon as list item 3 one if you want Ajbibb (talk) 19:52, 21 October 2013 (UTC)

synclient

To my experience, synclient refuses to change i.e. the parameter RightButtonAreaBottom (by giving a BadValue error) as long as MiddleButtonAreaRight==RightButtonAreaLeft. Not before I adjusted MiddleButton and RightButton to be real adjacent – by increment RightButtonAreaLeft, synclient accepted changes to RightButtonAreaBottom and MiddleButtonAreaBottom.

In my example I started with

   RightButtonAreaLeft     = 3443
   RightButtonAreaRight    = 0
   RightButtonAreaTop      = 0
   RightButtonAreaBottom   = 3306
   MiddleButtonAreaLeft    = 2636
   MiddleButtonAreaRight   = 3443
   MiddleButtonAreaTop     = 0
   MiddleButtonAreaBottom  = 3306

Trying

$ synclient MiddleButtonAreaBottom=2450

results

X Error of failed request:  BadValue (integer parameter out of range for operation)
 Major opcode of failed request:  131 (XInputExtension)
 Minor opcode of failed request:  37 (X_ChangeDeviceProperty)
 Value in failed request:  0x129
 Serial number of failed request:  22
 Current serial number in output stream:  25

After

$ synclient RightButtonAreaLeft=3444

both

$ synclient MiddleButtonAreaBottom=2450
$ synclient RightButtonAreaBottom=2450

gave no more errors.

As this is, in my opinion, a somewhat surprising behaviour, I'd add a note about this in the synclient-section. Ok? -- Peter0 (talk) 22:30, 22 June 2014 (UTC)