Bug 490739 - so i am on fedora 40. The bug i found is whenever i happen to focus on search bar particularly with Ctrl + f shortcut i cannot enter words in the bar. If i focus on the search bar using my mouse its working normal. Only when i use Ctrl +f issue occurs.
Summary: so i am on fedora 40. The bug i found is whenever i happen to focus on search...
Status: RESOLVED DUPLICATE of bug 438689
Alias: None
Product: systemsettings
Classification: Applications
Component: Quick Settings (other bugs)
Version First Reported In: 6.1.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-24 03:40 UTC by Rohit
Modified: 2024-07-24 17:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed 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 Rohit 2024-07-24 03:40:52 UTC 
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
so i am on fedora 40. The bug i found is whenever i happen to focus on search bar particularly with Ctrl + f shortcut i cannot enter words in the bar. If i focus on the search bar using my mouse its working normal. Only when i use Ctrl +f issue occurs.

STEPS TO REPRODUCE
1. Open settings
2. press Ctrl + f to focus on search bar
3. try to type something like `power`

OBSERVED RESULT
nothing gets typed in the search bar.

EXPECTED RESULT
power gets typed in the search bar and power settings are filtered

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: fedora 40
(available in About System)
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
wayland
ADDITIONAL INFORMATION
Comment 1 cwo 2024-07-24 17:27:47 UTC 
I can't reproduce this on Plasma 6.1.2 / Tuxedo OS.

Can you create a new user account, then log into that account and see if it works there? That would help determine whether there is a misbehaving setting in your current user, or whether it's a global problem.
Comment 2 cwo 2024-07-24 17:33:50 UTC 
Nevermind, I found a different report with explicit steps and was able reproduce the issue. Marking as a duplicate of that bug, please follow that one for updates on a fix. 464374 may also be relevant.

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