Bug 511465

Summary:	Allow a user to toggle visibility of settings pages such as joystick & touchscreen/touchscreen
Product:	[Applications] systemsettings	Reporter:	Cherkah <cherkaba>
Component:	sidebarview	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	kdedev, notmart
Priority:	NOR
Version First Reported In:	6.5.1
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Cherkah 2025-11-01 13:56:40 UTC

Hello, first of all, congratulations to you all on the latest version of KDE 6.5.1, which is really interesting... it's very polished :)

Regarding the settings application: how users can hide/disable accessory sections like "joystick" , "touchscreen" and some others? do you planned it ?
Version 6.5 already allowed users to hide the tablet component. For some, simply deleting the package removes its associated component, but for others, this isn't the case.

Indeed, neither my current hardware nor my needs  will use elements such as gaming, activities, Kaccounts..). These elements aren't so bothersome, but as the list keeps growing with each new feature (thanks again for night...!), it's becoming increasingly confusing to navigate it all and make system adjustments slower.

Why not create a catch-all category allowing users to hide only certain accessory components?
anyway thanks again.

EXPECTED RESULT
able to hide: joystick , touchscreen/touchpad, thunderbolt, kaccounts

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.5-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland

Comment 1 TraceyC 2025-12-08 23:23:28 UTC

If those settings pages could be toggled individually, that could make sense for users that don't have those components. They would have to be done individually rather than in a group. A system could have a touchscreen but no joystick, for instance.

Changing to wishlist, since this is a feature request and not a bug