Summary: | Mice connected after login always use Flat acceleration profile | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Frederick Zhang <frederick888> |
Component: | libinput | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | nate |
Priority: | NOR | ||
Version: | 5.25.4 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Frederick Zhang
2022-08-10 14:36:48 UTC
As a temporary workaround, one can change some settings, e.g. Pointer speed or Acceleration profile, in System Settings and change them back, then the newly connected mouse will start using Adaptive acceleration profile. *** This bug has been marked as a duplicate of bug 435113 *** Should I reopen this since the patch of bug 435113 didn't fix the problem for me? I'm using 5.25.4 which the patch was backported to. https://bugs.kde.org/show_bug.cgi?id=435113#c96 Also got framework 5.97.0 today and the issue still persists. $ pacman -Q $(pacman -Qq --groups plasma kf5) bluedevil 1:5.25.4-1 breeze 5.25.4-1 breeze-gtk 5.25.4-1 drkonqi 5.25.4-1 kactivitymanagerd 5.25.4-1 kde-cli-tools 5.25.4-1 kde-gtk-config 5.25.4-1 kdecoration 5.25.4-1 kdeplasma-addons 5.25.4-1 kgamma5 5.25.4-1 khotkeys 5.25.4-1 kinfocenter 5.25.4-1 kmenuedit 5.25.4-1 kscreen 5.25.4-1 kscreenlocker 5.25.4-1 ksshaskpass 5.25.4-1 ksystemstats 5.25.4-1 kwallet-pam 5.25.4-1 kwayland-integration 5.25.4-1 kwin 5.25.4-1 kwrited 5.25.4-1 layer-shell-qt 5.25.4-1 libkscreen 5.25.4-1 libksysguard 5.25.4-1 milou 5.25.4-1 oxygen 5.25.4-1 oxygen-sounds 5.25.4-1 plasma-browser-integration 5.25.4-1 plasma-desktop 5.25.4-1 plasma-disks 5.25.4-1 plasma-integration 5.25.4-1 plasma-nm 5.25.4-1 plasma-pa 5.25.4-1 plasma-sdk 5.25.4-1 plasma-thunderbolt 5.25.4-1 plasma-workspace 5.25.4-1 plasma-workspace-wallpapers 5.25.4-1 polkit-kde-agent 5.25.4-1 powerdevil 5.25.4-1 sddm-kcm 5.25.4-1 systemsettings 5.25.4-1 xdg-desktop-portal-kde 5.25.4-1 attica 5.97.0-1 baloo 5.97.0-1 bluez-qt 5.97.0-1 breeze-icons 5.97.0-1 extra-cmake-modules 5.97.0-1 frameworkintegration 5.97.0-1 kactivities 5.97.0-1 kactivities-stats 5.97.0-1 karchive 5.97.0-1 kauth 5.97.0-1 kbookmarks 5.97.0-1 kcmutils 5.97.0-1 kcodecs 5.97.0-1 kcompletion 5.97.0-1 kconfig 5.97.0-1 kconfigwidgets 5.97.0-1 kcontacts 1:5.97.0-1 kcoreaddons 5.97.0-1 kcrash 5.97.0-1 kdbusaddons 5.97.0-1 kdeclarative 5.97.0-1 kded 5.97.0-1 kdesu 5.97.0-1 kdnssd 5.97.0-1 kdoctools 5.97.0-1 kemoticons 5.97.0-1 kfilemetadata 5.97.0-1 kglobalaccel 5.97.0-1 kguiaddons 5.97.0-1 kholidays 1:5.97.0-1 ki18n 5.97.0-1 kiconthemes 5.97.0-1 kidletime 5.97.0-1 kinit 5.97.0-1 kio 5.97.0-1 kirigami2 5.97.0-1 kitemmodels 5.97.0-1 kitemviews 5.97.0-1 kjobwidgets 5.97.0-1 knewstuff 5.97.0-1 knotifications 5.97.0-1 knotifyconfig 5.97.0-1 kpackage 5.97.0-1 kparts 5.97.0-1 kpeople 5.97.0-1 kpty 5.97.0-1 kquickcharts 5.97.0-1 krunner 5.97.0-1 kservice 5.97.0-1 ktexteditor 5.97.0-1 ktextwidgets 5.97.0-1 kunitconversion 5.97.0-1 kwallet 5.97.0-1 kwayland 5.97.0-1 kwidgetsaddons 5.97.0-1 kwindowsystem 5.97.0-1 kxmlgui 5.97.0-1 modemmanager-qt 5.97.0-1 networkmanager-qt 5.97.0-1 plasma-framework 5.97.0-1 prison 5.97.0-1 purpose 5.97.0-1 qqc2-desktop-style 5.97.0-1 solid 5.97.0-1 sonnet 5.97.0-1 syndication 5.97.0-1 syntax-highlighting 5.97.0-1 threadweaver 5.97.0-1 Let's see if the original gets re-opened. It's possible it isn't actually fixed. |