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.
The X.Org libinput driver is a thin wrapper around libinput and allows for libinput to be used for input devices in X. This driver can be used as as drop-in replacement for evdev and synaptics. Simply build and install in your $PREFIX, then install the config file in /etc/X11/xorg.conf.d/. Restart X and the libinput driver will take over your devices.
Last edited by USUARIONUEVO; 03-12-2016 at 07:22 PM.
rworkman says works well on fedora, but nothing more.
Nothing more? Really?
These threads are ridiculous. I'd like to have dar, zpaq, postgresql, fcron, mksh, rxvt-unicode, racket and the forked heirloom-doctools included by default. Other people have their own lists. Where exactly do you want to stop?
Last edited by Gerard Lally; 03-12-2016 at 09:09 PM.
Hey , i say nothing more , around the libimput, i know rworkman works in slackware packages and slackbuilds a lot.
All my respect ,is a developer.
Im not need libimput , xf86-input-libimput , im not want, is only curiosity , because i read that package support touchscreens and other imput hardware , and im not sure why are not in slackware,only that.
@gezley
Ridiculous are people putting only trash , when users ask something, is a question , only a question , understand this?
that replaces 2 packages on xorg , but probably , the separate packages have more "hardware support" , or something...or not, i dont know, and i ask.
Richard Cranium , point to not big testing, then better go to work packages , and wait...probably is that.
I hope all can sleep this night after read this ridiculous thread. :=)
Last edited by USUARIONUEVO; 03-12-2016 at 09:15 PM.
And rworkman agrees that "libinput seemed to be a completely seamless transition for two machines here in front of me".
But Slackware-current is meant to be leading edge, not bleeding edge. A change in drivers for commonly used input devices is not to be undertaken lightly.
xf86-input-libinput is not part of mainstream Xorg's drivers yet. Libevdev and Libinput both have similar working stacks, but libinput was written for Wayland to give input support. Because Wayland isn't part of Slackware yet, libinput and xf86-input-libinput are not needed, and xf86-input-evdev and libevdev still work fine with X and programs that use it.
I'm certain that when Wayland is added, Patrick will probably consider xf86-input-libinput for inclusion, and if not, pass it off for the community if needed via SBo. Until then, you are free to craft and submit packages for it to SBo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.