This Week in KDE, Part 5 : Slider Bug Fix, Libinput UI on X11

Cheap talk

As most of the KDE people know, you can use Libinput on X11 but there are some issues with the combination of Libinput + X11 + Touchpad KCM. In KDE, when you use Libinput on X11, there will not be a special KCM support to handle Libinput settings. Fixing this issue is one of the main purpose of my Google Summer of Code adventure. And, the day has come! Our planning and discussions about the issue is done and the work is in progress. Let me give you some background information.

For touchpads, the situation is a little bit complicated. Touchpad has 2 possible display server choices in traditional PCs and different possibilities for input management libraries;
# Xorg
1. Evdev
2. Synaptics
3. Libinput

# Wayland
1. Libinput

So the KCM gets a little bit messy. Our plan is separating Wayland and Xorg KCMs into 2 different KCMs and showing the KCM to the user according to s/he’s backend. This will lead to a simpler KCM and simpler means easier to hack. After that, X11 will say welcome to its new Libinput KCM support 🙂 So basically the plan has 2 main parts. First part is on progress! We’ll deploy all the patches soon.

While working on the Libinput patch, a bug about Mouse/Touchpad KCM’s “Pointer Speed” slider is reported. The problem was that the slider was not totally accurate and we fixed the bug.

Show me the code

1. Mouse KCM Pointer Speed Slider Improvement patch is published. Commit is here.
2. Touchpad KCM Pointer Speed Slider Improvement patch is published. Commit is here.


Now, my todolist is as following:
1. Separating Touchpad KCM into 2 different KCMs: Touchpad KCM (Wayland, kcm_touchpad) and TouchpadX KCM (X11, kcm_touchpadX). Also by this patch, Touchpad KCM will be rewritten in KConfigModule.
2. Some cleaning in TouchpadX KCM.
3. Adding Libinput KCM support to X. By this patch, Bug 387153 will be fixed.

Hope to see you soon! 🙂

İlk yorum yapan olun

Bir yanıt bırakın