Summary: | (Enhancement) Implement changing the mouse acceleration profile of libinput in Wayland. | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | nmnazar43 |
Component: | libinput | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | bugseforuns, grmat, linux, nate |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
URL: | https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html | ||
Latest Commit: | Version Fixed In: |
Description
nmnazar43
2016-03-29 16:41:19 UTC
KWin currently does not yet have any configuration for libinput devices. Once that gets implemented the acceleration will also be implemented. The mouse acceleration settings from the mouse kcm are honored by kwin and mapped to the libinput acceleration. (In reply to Martin Gräßlin from comment #2) > The mouse acceleration settings from the mouse kcm are honored by kwin and > mapped to the libinput acceleration. Libinput supports different acceleration profiles: https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html The KCM offers selecting a factor, but not the profile. Therefore this issue is *not* yet resolved in 5.9. On x11 we can work around the missing kcm functionality by using xorg.conf files or xset, but that obviously is not a solution on wayland. As you have discovered, Libinput support here is poor to nonexistent. Fixing that is tracked with https://bugs.kde.org/show_bug.cgi?id=383379 As a workaround, you can either remove Libinput or configure it via .conf files if you're using Xorg: https://wiki.archlinux.org/index.php/Libinput#Configuration *** This bug has been marked as a duplicate of bug 383379 *** *** This bug has been marked as a duplicate of bug 350688 *** |