After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791136 - Settings search no longer search in settings and sub-headers
Settings search no longer search in settings and sub-headers
Status: RESOLVED DUPLICATE of bug 790755
Product: gnome-control-center
Classification: Core
Component: Search
3.26.x
Other Linux
: Normal enhancement
: ---
Assigned To: Cosimo Cecchi
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-12-02 16:33 UTC by Markus Igeland
Modified: 2017-12-02 23:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Markus Igeland 2017-12-02 16:33:50 UTC
After upgrading to Fedora 27, with Gnome 3.26.2, the search in settings no longer lets me search for a specific setting or a sub-section of settings.

In Fedora 26, on the Gnome version that was packed with Fedora 26 (I can't remember which version it was), I could search for, for example, «Night Light» or «Suspend», to find the settings under Devices>Displays (Night Light), or Power (Suspend & Power Button), but this is no longer possible. I miss this feature dearly, because I don't want to get to know all the available settings before using any single one of them. I know what setting I want to find, but not where it is located, so I need to be able to search for it.

I tried searching for other issues related to this, but I couldn't find any, but I'm still not sure if this is a duplicate or not.
Comment 1 Piotr Drąg 2017-12-02 22:03:32 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 790755 ***
Comment 2 Markus Igeland 2017-12-02 23:11:44 UTC
(In reply to Piotr Drąg from comment #1)
> Thanks for taking the time to report this.
> This particular bug has already been reported into our bug tracking system,
> but we are happy to tell you that the problem has already been fixed in the
> code repository.
> 
> *** This bug has been marked as a duplicate of bug 790755 ***

Awesome! Thanks a lot, Piotr! I'm sorry I didn't notice this was a duplicate.