gsynaptics-init won't load settings

Happens here too, newest Feisty.

I noticed something new (now on Fiesty also): Although the misspelling seems to have been fixed, my setting still don't reliably load.

** (gsynaptics-init:10682): WARNING **: Using synclient
Unknown parameter CoastingSpeedThreshold

When I first log in, the circular and vertical scrolling don't work, but if I try again some arbitrary time later, it DOES work. I've even put the CircularScrolling options directly in xorg.conf, yet the same issue remains.

Another suggestion:
The synaptics driver with SHMConfig enabled should be set up, and gsynaptics should be installed, if a touchpad is detected during setup. If it is made automatic, people won't have to deal with it manually, and it'll be far easier to disable tapping [assuming the other bug about the synaptics driver ignoring that setting has been fixed].

If the touchpad is made CorePointer and any other mice are set to use evdev with SendCoreEvents, then the secondary mouse will be hot-pluggable!

Is this the same problem that's been around since bug 3406 ?

The odd thing for me is that it does work... sometimes.
I'll log in to find the scrolling not working, but then after a while of normal usage, I'll suddenly note that the scrolling has started working. It seems really random to me.

The CoastingSpeedThreshold misspelling has been fixed, but I still get:
** (gsynaptics-init:21589): WARNING **: Using synclient
Unknown parameter CoastingSpeedThreshold

(no 'edit' or 'append' function....) Oh, and I also forgot this: somewhere along the line I manually put the relevant circularscrolling options directly into xorg.conf. (I used synclient directly to get the rightedge just perfect):
<snip....>

    Option "Emulate3Buttons" "true"
    Option "TapButton0" "0"
    Option "TapButton1" "0"
    Option "TapButton2" "0"
    Option "MaxTapTime" "0"
    Option "RightEdge" "5975"
    Option "CircularScrolling" "1"
    Option "CircScrollDelta" "0.234"
    Option "CircScrollTrigger" "3"
EndSection

Fixed in 0.9.7-3 in Feisty.

0.9.7-3 does not fix this problem.

The debbugs #401637 fixes only the spelling error in the error message, but does not fix this bug (#70525). The error message still occurs, and settings cannot be saved with the gsynaptics package.

The name of the attribute causing the error is (apparently) CoastingSpeed. Note no "Threshold" or "Threashold" or any other spelling at the end, just "CoastingSpeed".

After changing this in gsynaptics.c, it works properly and can save and restore settings with gsynaptics-init. (finally!)

This is for the synclient binary which comes with the package xserver-xorg-input-synaptics, which has the version 0.14.6-0ubuntu7, which is included in Feisty.

Not fixed in 0.9.7-3 in Feisty.

still not fixed in gutsy:

bash:~$ gsynaptics-init

** (gsynaptics-init:10859): WARNING **: Using synclient
Unknown parameter CoastingSpeedThreashold
bash:~$ gsynaptics-init --version
GNOME gsynaptics-init 0.9.12

Just another confirmation of this bug. Using Gutsy on a new Dell Inspiron 1420, gsynaptics 0.9.12. I'm going to pester Dell about getting behind fixing this and bug #133408, they need those fixed and gsynaptics pre-installed on their Ubuntu laptops.

the bug is present in gutsy
$ gsynaptics-init

** (gsynaptics-init:18215): WARNING **: Using synclient
Unknown parameter CoastingSpeedThreashold

it is very easy to fix this error, just modify the string containing
CoastingSpeedThreashold
maybe replacing it by just the first part of the name:
CoastingSpeed
that appears to be just a typing mistake
in the source files for:

$ grep -ir CoastingSpeedThreashold /usr/
Binary file /usr/X11R6/bin/gsynaptics-init matches
Binary file /usr/X11R6/bin/gsynaptics matches

I dont know how to modify that files in the repository, also I uninstalled thouchpad before reporting the bug.
neither I am 100% shure that the name replacement I suggested above is the intended behavior, because I haven't seen the source code.
I just browsed the object code discovering the string: "CoastingSpeedThreshold %s",
thus I inferred that this is part of a string format used to issue some code like

char format[]="something CoastingSpeedTreshold %s";
int value = some number;
....
sprintf(command,format,value);
system(command); or some of the exec family

I hope this helps to fix the problem. I regret not to know how to fix by my self being as easy as it seems because I am very busy at this moment to learn how.

Confirming exact same problem in Hardy.

I doubt this will get any attention any time soon, see:
http://bugzilla.gnome.org/show_bug.cgi?id=154029

I am still puzzled. How come upstrame has had a fix for the longest time and we don't ?

Still a problem in Intrepid as far as I can tell. I have "gsynaptics-init --sm-disable" in my startup sessions, but tapping is enabled until I run gsynaptics itself.

I take it back; I had a residual touchpad device section in my xorg.conf, and when I removed it, everything was good for me.

I take it back again. After a reboot, settings were again not loaded. It's broken.

Just want to confirm that to for 8.10, too.

terminal output was this:

$ gsynaptics-init

** (gsynaptics-init:6066): WARNING **: Using synclient
Unknown parameter CoastingSpeedThreshold
Unknown parameter ZoomIn
Unknown parameter ZoomOut
Unknown parameter RotateRight
Unknown parameter RotateLeft

Also it seems that it don't remember the settings concerning tabbing and scrolling. Tabbing is always enabled at start up, scrolling disabled.

This is what confuses me: gsynaptics-init 'sinfo page tells that there are no options for gsynaptics-init. Nevertheless the startup session entry comes up with:

gsynaptics-init --sm-disable

Still broken on jaunty.

barb@barb-laptop:~$ gsynaptics-init
GSynaptics couldn't initialize.
You have to set 'SHMConfig' 'true' in xorg.conf or XFree86.conf to use GSynaptics

barb@barb-laptop:~$ cat /etc/X11/xorg.conf
Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizScrollDelta" "20"
 Option "HorizEdgeScroll" "true"
 Option "SHMConfig" "true"
EndSection

How is it doing on the longevity prize?

Turning off mouseclicks from the pad helps

Well, it still isn't fixed in karmic... Oddly enough, the thing about remembering settings used to work until I upgraded to karmic, so it's probably an otherwise misconfiguration issue that exposes the bug, not a fresh install.

same bug in karmic here, too. also refuses to see any changes to /etc/X11/xorg.conf concerning SHMConfig.