antiX / MX LinuxThis forum is for the discussion of antiX and MX 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.
So it looks like I am using evdev. And unless I am misunderstanding your previous note, I shouldn't be using evdev. Is that correct?
Yes, I think you'd get better behaviour with libinput. I'm surprised that 'xserver-xorg-input-libinput' doesn't provide /etc/X11/xorg.conf.d/40-libinput.conf (or similar) as it does with other distros.
For example, my install (openSUSE Leap 15.0) has 40-libinput.conf with the following...
Not sure that is appropriate for Xfce 4.12 on Debian Stable. This comment from Dolphin_Oracle may be of interest:
Quote:
We actually added the 10-evdev.conf during MX-17 development to fix the otherwise non-functional mouse acceleration settings in Xfce-mouse-settings.
We looked at libinput and it is installed, but the 10-evdev.conf file probably forces use of the evdev drivers. The Xfce mouse settings (at least under our version from Debian) do not work very well with libinput (wheel settings could not be changed at all in some cases). Maybe that will be different in Buster.
That may be the case but for natural scrolling I still think it's worth a shot, and just use libinput CLI to adjust the mouse (if there are problems with configuring via the DE).
I will give it a shot over the weekend. Probably Sunday. I've got tons of work and kid shuffling stuff going on Friday/Friday night and Saturday.
[edit]
Since my libinput version is 0.23.0-2, should the file be named differently, like 23-libinput.conf? Or does the version have nothing to do with the file name?
So far every app I have tried scrolls "naturally."
Thank you everyone for your input (ha ha)!
So I created 40-libinput.conf, I edited 10-evdev.conf and commented out the mouse section, added a mouse section into libinput with the extra natural scroll option and rebooted. So far so good.
So far every app I have tried scrolls "naturally."
Thank you everyone for your input (ha ha)!
As I expected it would. There should have been no need to explicitly edit the 10-evdev.conf file though. The X-server should apply the directives from 40-libinput by precedence. Anyway, good to read that natural scrolling is now working for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.