Bug 1225579

As part of
https://fedoraproject.org/wiki/Changes/LibinputForXorg

libinput is used instead of (classic) synaptics driver, but it has less features, as you noted.

To switch away from libinput, remove the package
xorg-x11-drv-libinput

and reboot.  kcm_touchpad should then give more features (like edge scrolling customization)

Getting "No touchpad found", however can still move the pointer. All possible setting are now "disabled"

As per link above, it is mentioned:
change is limited to the Workstation product / the gnome-desktop

However I use KDE spin.

The description is not entirely accurate, kde spin uses it too.

Sorry about it not working properly after removing libinput driver, that's tracked in bug #1199825

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

Well, it may be a bug in kcm, however default setup still uses xorg-x11-drv-libinput, that lacks this important ability for notebooks. Any chance to fix this regression?

libinput is simply not as featureful as synaptics, you're welcome to file bug(s) against libinput if you wish (or would you rather we reassign this one?)

Yes, if you feel it has to go to libinput maintainers, then please reassign it to them.

Reassigning as requested

So far in this state the workaround is "synclient VertEdgeScroll=1". Hope you can find a proper solution.

For a writeup on why it is greyed out:
http://who-t.blogspot.com.au/2015/03/why-libinput-doesnt-support-edge.html


(In reply to Artur Cuvasov from comment #9)
> So far in this state the workaround is "synclient VertEdgeScroll=1". Hope
> you can find a proper solution.

fwiw, this has no effect if the libinput driver is active

> http://who-t.blogspot.com.au/2015/03/why-libinput-doesnt-support-edge.html
Makes sense, however it is not the best idea to forget about old believers who can not, or does not want to, use the new rich-featured library.

In my case, having 2 finger scrolling using libinput makes me slip several times before it starts working with interrupts. Classic edge scrolling, however, works like a charm.

> fwiw, this has no effect if the libinput driver is active
Yes, I had to remove libinput.

(In reply to Artur Cuvasov from comment #11)
> In my case, having 2 finger scrolling using libinput makes me slip several
> times before it starts working with interrupts. Classic edge scrolling,
> however, works like a charm.

that sounds like a bug and we should fix that separately. I'd need a evemu-recording please of such a two-finger motion that doesn't trigger so we can debug why it's not reliable.

Will do that later when back home. Anyways, that does not supersede the fact, that one might want to continue using a classic edge scrolling by simply choosing it via the systemsettings.

yeah, I understand. the problem is basically that with all the other features touchpads require these days, edge scrolling is really hard to fit in in a sensible manner, without introducing ambiguity on what happens when, etc.

So you decided to get rid of it completely? I do not think I am the only one who does not care about 2-finger scrolling or other modern features. The touchpad is used occasionally, and must be able to perform at least simple operations like old-non-fancy-edge-scrolling. Now it turns out that you have cut even basic operations for the ones who do not need extended features.

I hope you understand my point and might find it necessary to let people decide whether they want just basic functionality like move pointer / vertical and horizontal scroll, or modern reach-featured module.

we have the edge scroll implementation in the source and it's available on touchpads that need it. but as I said it conflicts with a number of other everyday features and that makes it difficult to integrate without giving up on a maintainable source.

For your use case I'd honestly rather try to fix the two-finger scrolling bug and then see how quickly you get used to two-finger scrolling.

*** Bug 1228691 has been marked as a duplicate of this bug. ***

*** Bug 1228786 has been marked as a duplicate of this bug. ***

libinput-0.19.0-2.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/libinput-0.19.0-2.fc22

Package libinput-0.19.0-2.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libinput-0.19.0-2.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-11448/libinput-0.19.0-2.fc22
then log in and leave karma (feedback).

libinput-0.19.0-2.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.