Bug 413514 - Pressing Alt+C triggers the Cancel button, not the Tap-to-click button
Summary: Pressing Alt+C triggers the Cancel button, not the Tap-to-click button
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.17.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: junior-jobs
Depends on:
Blocks:
 
Reported: 2019-10-27 11:29 UTC by joey.joey586
Modified: 2023-08-05 13:47 UTC (History)
2 users (show)

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


Attachments
Plasma settings touchpad dialog (107.53 KB, image/png)
2019-10-27 11:29 UTC, joey.joey586
Details

Note You need to log in before you can comment on or make changes to this bug.
Description joey.joey586 2019-10-27 11:29:16 UTC
Created attachment 123513 [details]
Plasma settings touchpad dialog

SUMMARY


STEPS TO REPRODUCE
1. Open settings manager
2. go to touchpad
3. use Alt+C to trigger the Tap-to-click checkbox

OBSERVED RESULT

Pressing Alt+C triggers the Cancel button, not the Tap-to-click checkbox, closing the Touchpad dialog. By default tap-to-click is disabled on Plasma desktop, so users without a physical mouse cannot enable touchpad tapping via keyboard.

EXPECTED RESULT

Pressing Alt+C should have triggered the Tap-to-click checkbox


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux, Kernel 5.3.7
(available in About System)
KDE Plasma Version: 5.17.1
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1

ADDITIONAL INFORMATION

I never had this problem with Kubuntu 17.10/18.04 (I forgot what version of Plasma that was); Alt+C was only assigned to Tap-to-click and not the Cancel button.
Comment 1 Nate Graham 2019-10-27 21:56:26 UTC
Needs the accelerator set to some other letter I guess.
Comment 2 Nate Graham 2023-08-05 13:47:57 UTC
Nowadays the KCM always opens in System Settings rather than KCMShell, and in System Settings, the Cancel button isn't shown. This means the bug has effectively been fixed for everyone except people who manually run `kcmshell{5,6} kcm_touchpad`. Fixing it there is not worth the effort given how niche of a use case this is; marking as (effectively) fixed.