After messing around with my 50-synaptics.conf file, a problem cropped up. After the computer goes to sleep or the lid is closed, the touchpad does not work. At first the touchpad still worked on the password entry screen, but now it is frozen there too. I thought it might have to do with some changes I made to 50-synaptics.conf but after commenting them out, the problem persisted. I tried disabling and re-enabling the KDE touchpad enabler, but to no avail.
synclient TouchpadOff=0
does not restore the touchpad even temporarily.
other details: shortly before this problem a rose I ran:
syndaemon -k -i 2 -d
But that was only active for that session as demonstrated by the fact that typing is not disabling the touchpad right now.
I also just installed mySQL server and started it. Stopping it did not alleviate the problem.
And here is the 50-synaptics.conf file contents, in case there is something weird about it that maybe I did uninetionionally
# Example xorg.conf.d snippet that assigns the touchpad driver
# to all touchpads. See xorg.conf.d(5) for more information on
# InputClass.
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
# Additional options may be added in the form of
# Option "OptionName" "value"
#
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
MatchDevicePath "/dev/input/event*"
Option "HorizScrollDelta" "0"
# enable tap-to-click as default (bnc#722457)
Option "TapButton1" "1"
Option "TapButton3" "2"
Option "TapButton2" "3"
EndSection
Section "InputClass"
Identifier "touchpad ignore duplicates"
MatchIsTouchpad "on"
MatchOS "Linux"
MatchDevicePath "/dev/input/mouse*"
Option "Ignore" "on"
EndSection
# This option enables the bottom right corner to be a right button on
# non-synaptics clickpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Default clickpad buttons"
MatchDriver "synaptics"
Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
# To disable the bottom edge area so the buttons only work as buttons,
# not for movement, set the AreaBottomEdge
# Option "AreaBottomEdge" "82%"
EndSection
# This option disables software buttons on Apple touchpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Disable clickpad buttons on Apple touchpads"
MatchProduct "Apple|bcm5974"
MatchDriver "synaptics"
Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
EndSection
Anybody have an ideas about what I might try next? Should I reinstall synaptics?
I don’t have a definite answer, but your 50-synaptics file looks the same as mine. (I’m not sure if it’s required, but check that you still have a EOF character after the last line perhaps?)
In any case to reinstall, you can do
zypper in --force xf86-input-synaptics
Reinstalled as per your instruction. Nothing. I googled a bit about this EOF character thing, but it’s not immediately clear to me what the EOF character I should put at the end of the file is.
I tried adding
^D
to the end of my file, but I think I’m misunderstanding what EOF means in this context because all that did is make it impossible to start X. I corrected the problem in vim.
So what is the proper way for me to include an explicit EOF? (this must be a really basic question, but google didnt give me anything that I could use)
Also, I updated my kernel to 3.16 earlier in the day, but the problem did not start until much later (after several successful wake ups).
Edit: It is the kernel, the problem went away when I booted into 3.11
Unfortunately my wifi doesn’t work properly under 3.11.
Just a blank line ie hit enter at the end of the last entry. I’m not sure that it is even necessary, although I’ve encountered situations where it was. (Just can’t remember what.)
It might be useful to report current reported status from
synclient -l
Ok adding a blank line to the end didn’t help. Here is the output (not from while it is frozen)
synclient -l
Parameter settings:
LeftEdge = 49
RightEdge = 1187
TopEdge = 48
BottomEdge = 850
FingerLow = 25
FingerHigh = 30
MaxTapTime = 180
MaxTapMove = 67
MaxDoubleTapTime = 180
SingleTapTimeout = 180
ClickTime = 100
EmulateMidButtonTime = 75
EmulateTwoFingerMinZ = 282
EmulateTwoFingerMinW = 7
VertScrollDelta = 30
HorizScrollDelta = 0
VertEdgeScroll = 0
HorizEdgeScroll = 0
CornerCoasting = 0
VertTwoFingerScroll = 1
HorizTwoFingerScroll = 0
MinSpeed = 1
MaxSpeed = 1.75
AccelFactor = 0.130976
TouchpadOff = 0
LockedDrags = 0
LockedDragTimeout = 5000
RTCornerButton = 0
RBCornerButton = 0
LTCornerButton = 0
LBCornerButton = 0
TapButton1 = 1
TapButton2 = 3
TapButton3 = 2
ClickFinger1 = 1
ClickFinger2 = 3
ClickFinger3 = 2
CircularScrolling = 0
CircScrollDelta = 0.1
CircScrollTrigger = 0
PalmDetect = 0
PalmMinWidth = 10
PalmMinZ = 200
CoastingSpeed = 20
CoastingFriction = 50
PressureMotionMinZ = 30
PressureMotionMaxZ = 160
PressureMotionMinFactor = 1
PressureMotionMaxFactor = 1
GrabEventDevice = 1
TapAndDragGesture = 1
AreaLeftEdge = 0
AreaRightEdge = 0
AreaTopEdge = 0
AreaBottomEdge = 0
HorizHysteresis = 7
VertHysteresis = 7
ClickPad = 0
Also, I updated my kernel to 3.16 earlier in the day, but the problem did not start until much later (after several successful wake ups).
Edit: It is the kernel, the problem went away when I booted into 3.11
Unfortunately my wifi doesn’t work properly under 3.11.
I didn’t see your earlier post about changing kernels, so it is not a configuration issue like we were initially led to believe.
So I guess my options are:
- Downgrade kernel and deal with my previous wifi problems
- Keep the new kernel and deal with the touchpad problems
- Install a Tumbleweed kernel and see how that works on my system.
- Wait and hope an update fixes my problem.
- Admit defeat and see if another distro works better on this machine (ACER V3-572-5217 )
Are there any additional options I’m not thinking of?
Is Tumbleweed stable enough work/desktop use?
Additional info.
I just tried plugging in a mouse, and that worked perfectly (while the touchpad was unresponsive).
I guess kernel 3.16 doesnt like my specific touchpad.
If an earlier kernel supported your touchpad, then that is a regression with the later kernel driver. Worth submitting a bug report IMO.
Option 1 may well be easier to deal with, but it depends on your hardware. You could start a new thread for that if necessary.
- Install a Tumbleweed kernel and see how that works on my system.
- Wait and hope an update fixes my problem.
- Admit defeat and see if another distro works better on this machine (ACER V3-572-5217 )
Are there any additional options I’m not thinking of?
Is Tumbleweed stable enough work/desktop use?
I can’t offer advice about these options.
Hmm there have been a bunch of threads about option 1 and I’ve already done the stuff suggested there… maybe I will start another thread and see if anyone has any new suggestions. Anyway thanks for your time!