Bug 474750 - Touchpad and KWin shortcut settings change on update
Summary: Touchpad and KWin shortcut settings change on update
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (other bugs)
Version First Reported In: 5.27.8
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 474751 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-09-21 01:46 UTC by Gabriel Del
Modified: 2024-02-16 21:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.27.9
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriel Del 2023-09-21 01:46:11 UTC 
SUMMARY


STEPS TO REPRODUCE
1. System settings -> Input devices -> Touchpad -> [scrolling] "invert scroll direction" unselect
2.  Update sytem, including kde

OBSERVED RESULT
The "invert scroll direction" are still unselected but with the behavior of selected.
Then it's necessary to select, unselect, apply to return to normal.


EXPECTED RESULT
That settings do not change in updates

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-09-21 16:04:13 UTC 
Are you using Plasma from git master, or 5.27.8? The bug report says both. :)
Comment 2 Nate Graham 2023-09-21 16:04:46 UTC 
Because if you're using git master, this is fixed with https://invent.kde.org/plasma/plasma-desktop/-/commit/0d59c07717c640382a1b35dcdf7e9189b2cbe57f.

If you're not... eek.
Comment 3 Gabriel Del 2023-09-21 16:48:11 UTC 
(In reply to Nate Graham from comment #2)
> Because if you're using git master, this is fixed with
> https://invent.kde.org/plasma/plasma-desktop/-/commit/
> 0d59c07717c640382a1b35dcdf7e9189b2cbe57f.
> 
> If you're not... eek.

I'm installing directly from Pacman on Garuda Linux: plasma-desktop-5.27.8-1
Comment 4 Nate Graham 2023-09-25 19:09:48 UTC 
*** Bug 474751 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2024-02-16 21:15:28 UTC 
Ok, then it's fixed in 5.27.9.