[Bug 979554] New: Since switch to libinput, circular scrolling doesn't work
http://bugzilla.opensuse.org/show_bug.cgi?id=979554 Bug ID: 979554 Summary: Since switch to libinput, circular scrolling doesn't work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: ivan.topolsky@isb-sib.ch QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Hello, since Tunbleweed switched from "synaptics" to "libinput" driver for touchpads a few week back, "Circular Scrolling" isn't available anymore for the "AlpsPS/2 ALPS DualPoint TouchPad" on my Dell Lattitude e6510.
libinput Scroll Methods Available (291): 1, 1, 0 libinput Scroll Method Enabled (292): 0, 1, 0 libinput Scroll Method Enabled Default (293): 1, 0, 0
It's either "Two fingers" by default, or "Edge Scroll" after setting it in systemsettings5 (as in the above exemple). No circular scrolling available anymore as it used to be the case with the synaptics driver. What's the best course of action for me ? - revert/downgrade back to synaptics driver ? - or is there some beta version of libinput *with* circular scrolling that I can try ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=979554
http://bugzilla.opensuse.org/show_bug.cgi?id=979554#c1
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=979554
http://bugzilla.opensuse.org/show_bug.cgi?id=979554#c2
--- Comment #2 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=979554
http://bugzilla.opensuse.org/show_bug.cgi?id=979554#c3
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=979554
http://bugzilla.opensuse.org/show_bug.cgi?id=979554#c4
--- Comment #4 from Egbert Eich
Reopen in order to track which input drivers being installed by default and with which priority these are chosen by X. Reassigning to myself.
Stefan, I'm not sure if this is a good idea. For Wacom we can do this as we have a pretty good idea about device IDs which are supported by the xf86-input-wacom driver. As mentioned in comment #1 Synaptics only has the 'catch all' rule 'MatchIsTouchpad'. So all devices with the 'touchpad' property will match. Which may include some touchpad devices which are not Synaptics. What we could do howeer, is to give *-synaptics.conf an higher priority than libinput and no longer install the synaptics driver by default. This way, whoever wants to take advantage of the additional features of the Synaptics driver can just go and install it to get them without renaming any files or changing any config files. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=979554
http://bugzilla.opensuse.org/show_bug.cgi?id=979554#c5
Stefan Dirsch
(In reply to Stefan Dirsch from comment #3)
Reopen in order to track which input drivers being installed by default and with which priority these are chosen by X. Reassigning to myself.
Stefan, I'm not sure if this is a good idea. For Wacom we can do this as we have a pretty good idea about device IDs which are supported by the xf86-input-wacom driver. As mentioned in comment #1 Synaptics only has the 'catch all' rule 'MatchIsTouchpad'. So all devices with the 'touchpad' property will match. Which may include some touchpad devices which are not Synaptics.
What we could do howeer, is to give *-synaptics.conf an higher priority than libinput and no longer install the synaptics driver by default. This way, whoever wants to take advantage of the additional features of the Synaptics driver can just go and install it to get them without renaming any files or changing any config files.
This would have been my plan. Only install libinput by default. And give also synaptics and evdev a higher conf priority. If one installs one of these drivers manually he should get it. Another pro is that users updating the system won't get migrated to libinput, which obviously has a different set of features. Current conf priority plan: libinput: 060 (upstream prio) evdev: 065 (patch), remove Supplements: xorg-x11-server wacom: 070 (upstream prio), remove Supplements: xorg-x11-server synaptics: 070 (patch), remove Supplements: xorg-x11-server -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=979554
http://bugzilla.opensuse.org/show_bug.cgi?id=979554#c6
--- Comment #6 from Egbert Eich
libinput: 060 (upstream prio) evdev: 065 (patch), remove Supplements: xorg-x11-server wacom: 070 (upstream prio), remove Supplements: xorg-x11-server
Don't remove. The matching rules are precise enough to only get you the Wacom driver for Wacom devices. This driver gives you a considerable advantage over libinput.
synaptics: 070 (patch), remove Supplements: xorg-x11-server
I would not use a patch either. I'd use 'mv' in the install section ;) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=979554
http://bugzilla.opensuse.org/show_bug.cgi?id=979554#c7
--- Comment #7 from Stefan Dirsch
(In reply to Stefan Dirsch from comment #5)
libinput: 060 (upstream prio) evdev: 065 (patch), remove Supplements: xorg-x11-server wacom: 070 (upstream prio), remove Supplements: xorg-x11-server
Don't remove. The matching rules are precise enough to only get you the Wacom driver for Wacom devices. This driver gives you a considerable advantage over libinput.
Ok. Convinced.
synaptics: 070 (patch), remove Supplements: xorg-x11-server
I would not use a patch either. I'd use 'mv' in the install section ;)
The intention of the patch is to push it also upstream with the same reasoning as with wacom. So everybody can benefit - or suffer;-) - from it. ;-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=979554
http://bugzilla.opensuse.org/show_bug.cgi?id=979554#c8
--- Comment #8 from Egbert Eich
The intention of the patch is to push it also upstream with the same reasoning as with wacom. So everybody can benefit - or suffer;-) - from it. ;-)
Sure, you can give it a try. Not sure if this will be successful, though. Most users seem to be content with the features the libinput driver offers for touchpads. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com