Bug 1399614 - RFE: Make libinput inherit configuration from synaptics
Summary: RFE: Make libinput inherit configuration from synaptics
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libinput
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 12:27 UTC by Zuzana Svetlikova
Modified: 2016-11-29 20:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-29 20:49:37 UTC
Type: Bug


Attachments (Terms of Use)

Description Zuzana Svetlikova 2016-11-29 12:27:27 UTC
Description of problem:
Create 30-touchpad.conf automatically from synaptics.conf, so users don't have to

Version-Release number of selected component (if applicable):
libinput-1.5.2-2.f26

How reproducible:
always

Steps to Reproduce:
1.Switch to libinput
2.Touchpad doesn't work as it used to
3.I have to create another config file to make it work

Actual results:
Transition from synaptics to libinput isn't very smooth

Expected results:
Everything works as before

Additional info:

Comment 1 Peter Hutterer 2016-11-29 20:49:37 UTC
One of the main reasons why xorg-x11-drv-synaptics and xorg-x11-drv-libinput don't share the same config options is that most of the synaptics ones aren't available in libinput and/or the other way round. e.g. synaptics doesn't have a left-handed configuration. libinput OTOH doesn't have the click actions, it merely has the "set click method" approach.

when we started with the xorg-x11-drv-libinput driver upstream we discussed making the two compatible but it's not realistic to do so and the time and effort spent (and keeping compatibilty forever) would outweigh the benefit gained from it.

Another problem is that many of the config options I see in the wild are blindly copied from some forum, so it's hard to even be sure what options a user wanted to set in the first place. I've seen things where a snippet claims to change pointer acceleration and instead disables scrolling, and similar.

Long-term it's much easier for everyone to take the hit of one-time reconfiguration of the touchpad and move on.

Sorry, this is a wontfix.


Note You need to log in before you can comment on or make changes to this bug.