Bug 403727

Could you please attach the complete xorg.conf and /var/log/Xorg.0.log when started with the original xorg.conf created by SaX2? Thanks.

Created attachment 233441 [details]
xorg.conf as configured by openSUSE

As requested here is the original xorg.conf.  I had to edit this file as stated in the bug report to get the touchpad to work.

> InputDevice  "Mouse[1]" "CorePointer"
> InputDevice  "Mouse[3]" "SendCoreEvents"

Looks good. Xorg.0.log is still missing. See my comment #1.

Created attachment 233560 [details]
Xorg.0.log

Sorry I posted xorg.conf instead of this log.  I noticed during the test that the touchpad works when logging in, but then fails to respond once the gnome session loads.

(II) Synaptics touchpad driver version 0.14.6 (1406)
(--) Mouse[1] auto-dev sets device to /dev/input/event2 (waited 0 msec)
(**) Option "Device" "/dev/input/event2"
(**) Option "SHMConfig" "on"
(**) Option "HorizScrollDelta" "0"
(--) Mouse[1] touchpad found
(**) Option "CorePointer"
(**) Mouse[1]: always reports core events
(**) Option "Protocol" "explorerps/2"

Looks good. Maybe GNOME runs gsynaptics or synclient directly to break the synaptics driver settings. Please do the following:

Chose Failsafe as Xsession instead of GNOME in displaymanager. Then run

  synclient -l > /tmp/failsafe

in the xterm, which is started. Type 'exit' to log out. Select GNOME as
Xsession again in displaymager. Run

  synclient -l > /tmp/gnome

in a terminal. Attach both files to this bugreport. Thanks.

With the original configuration in place of course ...

Does other Xsessions like KDE3, KDE4 or Xfce also break the synaptics touchpad?

Created attachment 233644 [details]
synclient -l > /tmp/gnome

Created attachment 233645 [details]
synclient -l > /tmp/failsafe

Just tested with xfce and the problem is not exhibited there.  So it must be something specific to gnome.

--- failsafe    2008-08-15 20:24:19.000000000 +0200
+++ gnome       2008-08-15 20:24:08.000000000 +0200
@@ -3,8 +3,8 @@
     RightEdge            = 5400
     TopEdge              = 1900
     BottomEdge           = 4000
-    FingerLow            = 25
-    FingerHigh           = 30
+    FingerLow            = 53
+    FingerHigh           = 58
     MaxTapTime           = 180
     MaxTapMove           = 220
     MaxDoubleTapTime     = 180
@@ -18,9 +18,9 @@
     HorizEdgeScroll      = 1
     VertTwoFingerScroll  = 0
     HorizTwoFingerScroll = 0
-    MinSpeed             = 0.09
-    MaxSpeed             = 0.18
-    AccelFactor          = 0.0015
+    MinSpeed             = 0
+    MaxSpeed             = 0
+    AccelFactor          = 0
     EdgeMotionMinZ       = 30
     EdgeMotionMaxZ       = 160
     EdgeMotionMinSpeed   = 1
@@ -42,7 +42,7 @@
     TapButton2           = 2
     TapButton3           = 3
     CircularScrolling    = 0
-    CircScrollDelta      = 0.1
+    CircScrollDelta      = 0.01
     CircScrollTrigger    = 0
     CircularPad          = 0
     PalmDetect           = 1

Setting MinSpeed to 0 is fatal. It will make the synaptics touchpad unusable.

I have been seeing exactly the symptoms described in Comment 4 above.

The machine works fine for a while, but on occasion after logging in the cursor stops responding to the synaptic touchpad.  The cursor works fine in gdm, and after entering a username, all the while the grey thing called "the panel" is being iterated across with little icons.  As soon as that stops - with nmApplets - the cursor freezes.

The right-click button can be used to bring up a menu on the desktop, and if I use that to open a terminal and run synclient -m 100 the touchpad is still seen working normally through that.

Once a user login has got into this state, it can not normally be recovered.  I have had limited success with deleting /tmp/gconf-<user> before logging in, but usually the login is borked.  If you log in using KDE or another desktop the cursor works fine.  It is only Gnome - and the Gnome failsafe - that are broken.


My first attempts to work around have been to:
create a new user, 
rename the broken user directory in /home, to a safe name
cp -R the new user directory to replace the broken one
chown -R the replacement with the correct credentials for the login.

Loging in as the affected user now gives a login that works with the cursor but has lost all the customisation, data and mail, which have to be copied piecemeal from the safe name or re-created.

This is a dirty process and I have been trying to use ls -lt -c to find what the most recently changed files have been.  This bug report gives me further clues but I would also like to add my voice to the complaints about the behaviour and the lack of obvious information in any of the system logs to help identitfy what was going on.

Let me end this saga with an account of inducing this problem - not entirely reproducable but has recurred intermittently.  Open the menu and 'Control Center' (sic).  Find Hardware - Touchpad .  Select the 'tapping' tab and untick 'tapping' - and the cursor may well instantly freeze on you and become frozen even if you ctrl-alt-backspace and log in again, or reboot.

It is beginning to look like it only goes wrong when tapping is turned off somehow - using the control centre, or a profile script to call synclient, or putting an option in xorg.cong - but I cannot be precise about that, that may just be when the config is updated and that causes the fatal setting described in comment 4 to be written.

It just happened to me again.  I am now running KDE, Deleting /tmp/gconf-bobh did not cure the problem.
----------------------------------------------
/home/bobh.new/.gconf/desktop/gnome only contains accessibility and an empty %gconf.xml  . This is a copy of a working home directory.
------------------------------------------------------------------------------
/home/bobh.old/.gconf/desktop/gnome/peripherals/touchpad contains the following %gconf.xml
<?xml version="1.0"?>
<gconf>
        <entry name="vert_scroll_delta" mtime="1224096461" type="int" value="100">
        </entry>
        <entry name="max_tap_time" mtime="1224096461" type="int" value="180">
        </entry>
        <entry name="off" mtime="1224096461" type="bool" value="false">
        </entry>
</gconf>
This is a copy of a broken home directory.
------------------------------------------------------------------------------
The .xesssession-errors from the broken one contains 
** (gsynaptics-init:5736): WARNING **: Using synclient
Unknown parameter CoastingSpeedThreshold
INFO (main:38) No docking station detected, exiting...

The same file from the working directory contains
** (gsynaptics-init:6267): WARNING **: Using synclient
INFO (main:38) No docking station detected, exiting...

Where is it reading CoastingSpeedThreshold from?  I will attach the output of synclient -l, which does indeed not include CoastingSpeedThreshold

Created attachment 245772 [details]
Synclient -l from bob Harvey to accompany comment 12

This bug seem to be a dublicate to 402864 "Touchpad Stops Working" https://bugzilla.novell.com/show_bug.cgi?id=402864.
Maybe someone can merge them?

That's curious.
the severity and priority of 402864 is a lot higher than this one.  How can that be?

This is driving me crazy.  I really need to turn off 'tapping' on my keypad, but because of this bug I cannot.

What plans are there for dealling with it?

*** This bug has been marked as a duplicate of bug 402864 ***