TouchPad doesn't click anymore after updating to -current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
TouchPad doesn't click anymore after updating to -current
Hi everybody!
I'm used to update to -current almost once a week. Really doesn't cost me anything doing a: slackpkg update; slackpkg upgrade-all;
I really appreciated the -current X.org update, thanks to the wonderful team of Slackware!!!
Although I think this update messed up some pointer-related stuff.
The update caused my Vaio-Touchpad not to click anymore! I'm obliged to use the buttons to click. I don't know if it matters with the sensibility of the touchpad but a normal touch in the console does the trick, but in X not.
Also I've noticed a speed increase of the pointer (now adjusted through the KDE utility).
This issue is very strange as the update didn't touch the xorg.conf.
This is my xorg.conf:
My slackware is -current (X.org 1.6.1) running on a self-compiled 2.6.29 kernel (unchanged after the update).
I really don't have hints on how to fix this issue,
Thank you for the attention,
Karimo
Click here to see the post LQ members have rated as the most helpful post in this thread.
Have you tried it without any xorg.conf file at all? The new X is supposed to detect everything correctly via HAL. Try backing up and moving your xorg.conf file and start X and see if everything works. It may not work, but I have been surprised at how sometimes it does get everything right. You can always move your xorg.conf back afterwards.
Another idea is to try autogenerating a new xorg.conf file with 'Xorg -configure' and then try the resulting /root/xorg.conf.new.
Your configuration solved the problem.
The strange thing is that I've tried a similar configuration that I've seen over the synaptics-driver webpage. It was like this:
As you can see, the two configs are quite similars; except that this one has some more options.
Experimenting a bit I have figured out that commenting out the *Edge Options the Tab-to-click magically reappers.
Seems that that options define too wide edge-zones, disabling therefore the Standard-Pad-Zone with its Tab-to-click feature.
Everyone has fixed his issues at this point?
If you are in doubt if this configurations are for you because you don't know if you have a synaptics touchpad or if it is supported by the driver, take a look at this laptop compatibility list:
If you are running with the latest -current update from June 10th?, the xorg packages were all updated. I saw one other thread on here about how your Input Devices should not be specified in the server layout section because xorg now grabs all that information from HAL. But I don't know how this works with special input devices.
running "slackpkg clean-system" may help you clean up old x packages in case anything might be conflicting. You should be presented an ncurses menu to deselect any packages you don't want removed.
1. remove the xorg.conf file (backup, whatever) to let hal do its thing
2. edit the hal policy in usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi
I found that it was necessary to edit this file since all the options in it are commented out by default. It seems that hal doesn't load the synaptics driver for the X server if there are no options specified.
Mine looks like this:
Code:
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.touchpad">
<merge key="input.x11_driver" type="string">synaptics</merge>
<!-- Arbitrary options can be passed to the driver using
the input.x11_options property since xorg-server-1.5. -->
<!-- EXAMPLES:
Switch on shared memory, enables the driver to be configured at runtime
<merge key="input.x11_options.SHMConfig" type="string">true</merge>
Maximum movement of the finger for detecting a tap
<merge key="input.x11_options.MaxTapMove" type="string">2000</merge>
Enable vertical scrolling when dragging along the right edge
<merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>
Enable vertical scrolling when dragging with two fingers anywhere on the touchpad
<merge key="input.x11_options.VertTwoFingerScroll" type="string">true</merge>
Enable horizontal scrolling when dragging with two fingers anywhere on the touchpad
<merge key="input.x11_options.HorizTwoFingerScroll" type="string">true</merge>
If on, circular scrolling is used
<merge key="input.x11_options.CircularScrolling" type="string">true</merge>
For other possible options, check CONFIGURATION DETAILS in synaptics man page
-->
<merge key="input.x11_options.SHMConfig" type="string">true</merge>
<merge key="input.x11_options.TapButton1" type="string">1</merge>
<merge key="input.x11_options.FastTaps" type="string">1</merge>
</match>
</device>
</deviceinfo>
2. edit the hal policy in usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi
3. Repeat after the next upgrade/rebuild of the hal package because your edits will be overwritten.
From CHANGES_AND_HINTS.TXT:
Code:
If you are using input hotplugging via HAL and a synaptics touchpad, then you
might need to copy /usr/share/hal/fdi/policy/11-x11-synaptics.fdi to
/etc/hal/fdi/policy/ and edit it to suit your needs. You can also use
synclient(1) to make changes "on the fly."
The new xorg doesn't automatically configure touchpads correctly when you specify the "auto" protocol and "mouse" driver. Slackware, by default, tries to use those in xorg.
You need to start using the synapatics driver. Here's the mouse part of my xorg.conf. TapButtons1 option enables tapping. Fast taps is useful too.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
TouchPad doesn't click anymore after updating to -current
Help!
