Bug 482030 - [6.0]missing touchpad gesture settings
Summary: [6.0]missing touchpad gesture settings
Status: RESOLVED DUPLICATE of bug 402857
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 6.0.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-29 14:11 UTC by Thomas-Luke Duffin
Modified: 2024-03-03 19:23 UTC (History)
3 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 Thomas-Luke Duffin 2024-02-29 14:11:15 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open system settings
2. Search "gestures"
3. Check results

OBSERVED RESULT
Nothing for touchpad gestures can be found

EXPECTED RESULT
Gestures section under mouse/touchpad or within touchpad settings page

I'd love for Gestures to be available within a single page with options for three and 4 finger swipes in each direction. In particular, I was hoping to change the Overview gesture from 4 fingers to 3, just because right now up/down three finger gestures aren't utilized by my system atm.


SOFTWARE/OS VERSIONS
Linux Kernel: 6.5.0-18-generic (64-bit)
KDE Neon: 6.0
KDE Plasma Version: 6.0.0 
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
I'm using Wayland exclusively and gestures *do* work, just that there's no way to configure them at all :(

PS: Happy 6.0 launch! It looks *beautiful* and honestly I've not had any major breaking issues which is a testament to your testing and bug-hunting <3
Comment 1 Nate Graham 2024-03-01 06:29:51 UTC
The settings aren't missing, they simply haven't been developed yet. :) 

I'm glad you;re otherwise having a good experience!

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