Bug 460644 - Mouse cursor Acceleration profile reset upon disconnect
Summary: Mouse cursor Acceleration profile reset upon disconnect
Status: RESOLVED DUPLICATE of bug 457928
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: 5.24.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-18 10:03 UTC by Joey Crockett
Modified: 2022-10-18 22:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joey Crockett 2022-10-18 10:03:18 UTC
SUMMARY
***
When a mouse is disconnected and reconnected, the acceleration profile is reset as "Adaptive", but is still shown as "Flat".
***


STEPS TO REPRODUCE
1. Have a mouse connected and set to "Flat" profile
2. Disconnect mouse
3. Reconnect mouse

OBSERVED RESULT
The pointer's acceleration profile clearly feels like "Adaptive", but the change is not shown in the settings dialogue. No difference, if the settings were closed inbetween or not. In order to restore normal function, one must set the profile to "Adaptive", click "Apply", set it back to "Flat" and click "Apply" again.

EXPECTED RESULT
The selected acceleration Profile should be applied to all new devices upon connection.

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: Release 15.4 / Kernel 5.14.21-150400.24.18-default (64-bit)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
This also happens, when a machine is resumed from standby and the mouse is connected via hubs (i.e. mouse -> usb socket on keyboard -> usb hub -> host). This is pure speculation, but it might be a result of the host needing to wake up the hubs before the mouse is seen and initialized again.
Comment 1 Nate Graham 2022-10-18 19:30:16 UTC

*** This bug has been marked as a duplicate of bug 457928 ***
Comment 2 Joey Crockett 2022-10-18 22:14:41 UTC
Oops. Genuinely didn't see that.
Thanks for moving me over :)