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 750083 - [Regression] Quick search doesn't work
[Regression] Quick search doesn't work
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2015-05-29 05:55 UTC by Milan Crha
Modified: 2015-06-01 07:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2015-05-29 05:55:03 UTC 
Using gtk3-3.16.3-1.fc22.x86_64. Run gtk3-demo->Pickers, click File or Folder->Other..., click into the list of files, start typing to get quicker to a file. Nothing happens. It used to work.
Comment 1 Emmanuele Bassi (:ebassi) 2015-05-29 11:53:48 UTC 
Not a regression: this was intentional.

See also:

 * bug 744205
 * bug 746916
 * bug 748672
Comment 2 Matthias Clasen 2015-05-29 12:45:04 UTC 
Well, to be honest: it is a regression, I just haven't found the amount of quiet time needed to come up with a fix.
Comment 3 Milan Crha 2015-06-01 07:50:15 UTC 
(In reply to Emmanuele Bassi (:ebassi) from comment #1)
>  * bug 744205

Recursive searches? (I'm moving with my rant to that bug report).

>  * bug 746916

Remote network shares are not applicable here.

>  * bug 748672

So this is the bug report, which is about the same and is still opened. Thus you didn't mean to close this as Fixed, but as a duplicate of it, possibly?

(In reply to Matthias Clasen from comment #2)
> Well, to be honest: it is a regression, I just haven't found the amount of
> quiet time needed to come up with a fix.

I'm not sure I've got the right meaning of this. Is it like "there are too many people complaining about the new GtkFileChooser behaviour that you do not have time to dive into the issue"?