Bug 451183 - Touchpad Settings Revert Back to Default When Logging in With Touchpad Controller Plugged In
Summary: Touchpad Settings Revert Back to Default When Logging in With Touchpad Contro...
Status: RESOLVED DUPLICATE of bug 435113
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.24.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-06 00:47 UTC by poudinkpopinski
Modified: 2022-03-22 03:28 UTC (History)
1 user (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 poudinkpopinski 2022-03-06 00:47:26 UTC
Summary:
Touchpad Settings Revert Back to Default When Logging in With Touchpad Controller Plugged In

Comment:
SUMMARY
A total of four controllers were tested: a Sony DualShock 3 (no touchpad), a Sony DualShock 4 (touchpad), a Sony DualSense (touchpad) and a Logitech F310 (no touchpad). Of these, only the DualShock 4 and the DualSense were affected by this issue. Changing Touchpad Settings will have no effect unless the System Settings are launched after the controller has been unplugged. If the controller has been unplugged and the System Settings are launched, the correct settings will be shown, but must be re-applied to actually become active. Replugging the controller after the settings have been corrected does not cause any issues. Wirelessly connecting the controllers was not tested.


STEPS TO REPRODUCE
1. Modify touchpad settings.
2. Quit your KDE Plasma session.
3. Plug in a DualSense.
4. Launch a new KDE Plasma session.

OBSERVED RESULT
The modified settings are no longer active.

EXPECTED RESULT
The modified settings being active.

SOFTWARE/OS VERSIONS
Linux: Fedora 35, Kernel 5.16.12-200 (64bit)
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Comment 1 Nate Graham 2022-03-22 03:28:53 UTC

*** This bug has been marked as a duplicate of bug 435113 ***