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 340078 - slow widget population interferes with keyboard navigation
slow widget population interferes with keyboard navigation
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.8.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
filechooser-retest-and-triage
Depends on:
Blocks:
 
 
Reported: 2006-04-29 02:11 UTC by Peter Eckersley
Modified: 2018-04-15 00:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Peter Eckersley 2006-04-29 02:11:26 UTC 
Even on a fairly fast system, it can take a second or two for the GtkGileChooser to populate the list of files in the current directory.  In the mean time, the Chooser collects keystrokes that are relevant to selecting a file, and remembers them, but misses the relevant files.
Comment 1 Federico Mena Quintero 2007-01-25 19:56:59 UTC 

*** This bug has been marked as a duplicate of 333319 ***
Comment 2 Peter Eckersley 2007-01-25 20:34:03 UTC 
This is a bug in the main GtkFileChooser, not in the location entry widget.  It isn't a dup of 333319.

(In reply to comment #1)
> 
> *** This bug has been marked as a duplicate of 333319 ***
>
Comment 3 Matthias Clasen 2018-02-10 05:18:15 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 4 Matthias Clasen 2018-04-15 00:14:37 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new