Bug 489142 - Searching for settings in system settings doesn't find results (only for settings page titles and a *few* settings work)
Summary: Searching for settings in system settings doesn't find results (only for sett...
Status: CONFIRMED
Alias: None
Product: i18n
Classification: Translations
Component: en_GB (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: en_GB translators/proof-readers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-24 20:52 UTC by Vorpal
Modified: 2024-07-02 09:34 UTC (History)
1 user (show)

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


Attachments
Screenshot of broken search (80.04 KB, image/png)
2024-06-24 20:52 UTC, Vorpal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vorpal 2024-06-24 20:52:15 UTC
Created attachment 170926 [details]
Screenshot of broken search

***
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
It seems searching for individual settings is broken in 6.1.0. This used to work before.

* I can still successfully search for settings on "General behaviour", but not on "Night light" or anywhere under "Mouse & touchpad".
* I can search for the titles of settings pages, that seems to work fine.

STEPS TO REPRODUCE
1. For example: try to search for "edge barrier" or "corner barrier" in System Settings.

OBSERVED RESULT
No results (see attached screenshot)

EXPECTED RESULT
Mouse & Touchpad -> Screen Edges should be shown in the example above.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Maybe it is related to locale (since it is searching for strings in the UI), just in case:

$ locale
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC=sv_SE.UTF-8
LC_TIME=sv_SE.UTF-8
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY=sv_SE.UTF-8
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER=sv_SE.UTF-8
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT=sv_SE.UTF-8
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
Comment 1 fanzhuyifan 2024-06-24 22:19:49 UTC
Yeah missing the en_GB localizations.
Comment 2 Vorpal 2024-07-02 09:34:15 UTC
(In reply to fanzhuyifan from comment #1)
> Yeah missing the en_GB localizations.

In that case it should probably search for the string in whatever text is displayed, however that fallback system works today.