Bug 507818 - Cannot focus Search box by tapping on touch screen
Summary: Cannot focus Search box by tapping on touch screen
Status: RESOLVED DOWNSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kwineffects (other bugs)
Version First Reported In: 6.3.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-03 16:45 UTC by Alexander Potashev
Modified: 2025-08-03 17:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
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 Alexander Potashev 2025-08-03 16:45:57 UTC 
SUMMARY
Cannot focus Search box by tapping on touch screen.

STEPS TO REPRODUCE
1. Run System Settings.
2. Type "zoom"
3. Use touch screen to tap on "Desktop Effects"
4. Use touch screen to tap on "Search..."

OBSERVED RESULT
Nothing happens. If I try typing text on the keyboard, it doesn't show up anywhere.

EXPECTED RESULT
Should focus the text input "Search..."

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux rodete 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.12.27-1rodete1-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 14 × Intel® Core™ Ultra 7 165U
Memory: 62.3 GiB of RAM
Graphics Processor: Mesa Intel® Graphics

ADDITIONAL INFORMATION
Comment 1 Bug Janitor Service 2025-08-03 17:33:40 UTC 
Thank you for the bug report!

However Plasma 6.3.4 no longer receives updates or maintenance from KDE; active versions are 6.4 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need help with Plasma 6.3.4, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE.

If you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.