protonscr

ctrl+F can't be used for searching words on a steampage within steam

steamclosed Steam clientDistro Family: ArchWeb Component
ValveSoftware/steam-for-linux#11546 · opened 2024-12-05 by CaptainCoward · updated 2026-01-09 · 10 comments · github
CCaptainCoward 2024-12-05 github

Your system information

Steam client version (build number or date):
Steam Beta Branch: Stable Client
Steam Version: 1733265492
Steam Client Build Date: Mon, Dec 2 10:26 PM UTC -08:00
Steam Web Build Date: Mon, Dec 2 10:20 PM UTC -08:00
Steam API Version: SteamClient021

Distribution (e.g. Ubuntu):
EndeavourOS

Opted into Steam client beta?: [Yes/No]
No

Please describe your issue in as much detail as possible:

When attempting to search any steam page by ctrl+F you can't actually enter text for searching

Steps for reproducing this issue:

  1. Just go to any game page or achievement page and try to search via ctrl+f.
  2. You can't enter text in the search menu.
Kkisak-valve maintainer 2024-12-05 github

Hello @CaptainCoward, it works here in a quick test. Please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

CCaptainCoward 2024-12-06 github

Hey, i have tested it on 3 of my systems and it doesn't work on any of them. I'll post my mainsystem. If the others are needed as well i can provide a gist for them also. They all run EndeavourOS.
https://gist.github.com/CaptainCoward/e65eef72fce6fafc1e6c94e17ee29fb5

RRND2015 2024-12-11 github

I'm also having this issue on two separate machines with entirely different hardware. One is a laptop running Fedora Workstation, the other is a desktop running Fedora KDE. This issue happens on both the RPM and Flatpak version of Steam. Here is the system info for the laptop:
https://gist.github.com/RND2015/80636b5d15c23c055906b8ac483804f6

Edit: Enrolling in the Steam beta seems to have resolved this for the time being?

Vvic-bay 2025-03-29 github

looks like this is wayland issue caused by input isolation for focused windows only. popup search field is treated as a separate window but fails to grab keyboard focus

you can work around it on KDE Plasma

System Settings -> Application Permissions -> Legacy X11 App Support
and change Allow legacy X11 apps to read keystrokes typed in all apps to Always

be careful, it exposes all your input to every program, so keyloggers might steal your passwords

Eeciervo 2025-04-09 github

Same here in Arch Linux KDE Plasma 6.3.4 + Wayland.
Steam Beta also has this issue for me, but the workaround suggested by @vic-bay works.

DDamglador 2025-07-16 github

Same issue. Allowing X11 apps to capture everything in Plasma permissions settings fixed it. Thanks, vic-bay

Vvic-bay 2026-01-03 github

The bug seems to be fixed now.

I checked CTRL+F search feature in Steam client today, and the bug isn't there anymore, the input area works fine, I can enter text without issues. Double checked "Legacy X11 App Support" settings in KDE to make sure I don't have it enabled.

OS: Arch Linux x86_64
Kernel: Linux 6.18.1-arch1-2
DE: KDE Plasma 6.5.4
WM: KWin (Wayland)
CPU: AMD Ryzen 7 3700X (16) @ 4.43 GHz
GPU: NVIDIA GeForce RTX 2070 SUPER [Discrete]

Would be nice if someone could test it as well.

DDamglador 2026-01-03 github

Yup, seems to work fine now.

Eeciervo 2026-01-04 github

The bug seems to be fixed now.

I checked CTRL+F search feature in Steam client today, and the bug isn't there anymore, the input area works fine, I can enter text without issues. Double checked "Legacy X11 App Support" settings in KDE to make sure I don't have it enabled.

OS: Arch Linux x86_64
Kernel: Linux 6.18.1-arch1-2
DE: KDE Plasma 6.5.4 WM: KWin (Wayland)
CPU: AMD Ryzen 7 3700X (16) @ 4.43 GHz
GPU: NVIDIA GeForce RTX 2070 SUPER [Discrete]

Same here with a similar software and hardware configuration (also a Ryzen CPU and a Radeon 7900 XTX as GPU).
Steam Version: 1766451605 (Stable ch.)

CCaptainCoward 2026-01-09 github

can confirm it seems t o be fixed at this point. Therefore i'm closing the issue.

Nothing extracted yet.