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 167673 - GtkFileChooserDialog slow to open my home directory
GtkFileChooserDialog slow to open my home directory
Status: RESOLVED DUPLICATE of bug 166601
Product: gtk+
Classification: Platform
Component: Widget: Other
2.6.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-02-17 04:25 UTC by Billy Biggs
Modified: 2005-02-18 16:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Billy Biggs 2005-02-17 04:25:24 UTC
Debian unstable, GTK+ 2.6.2, libgnomevfs2-0 2.8.3-11.

Something seems wrong.  When I run the following program, which opens a file
chooser on my home directory, it hangs for a good 8-10 seconds before the watch
pointer goes away.  For almost all of that time, the GUI is blocked, and moving
windows over top of the dialog shows that it is not responding to expose events.

For comparison, the old file chooser widget loads my home directory instantly. 
My home directory has 262 non-hidden directories and 543 files in it of various
types.  It is not NFS mounted.

int
main (int argc, char **argv)
{
    GtkWidget *chooser;
    gtk_init (&argc, &argv);
    chooser = gtk_file_chooser_dialog_new ("...slow...",
                  GTK_WINDOW (window), GTK_FILE_CHOOSER_ACTION_OPEN,
                  GTK_STOCK_CANCEL, GTK_RESPONSE_CANCEL, GTK_STOCK_OK,
                  GTK_RESPONSE_OK, NULL);
    gtk_file_chooser_set_current_folder (GTK_FILE_CHOOSER (chooser),
                                         getenv ("HOME"));
    gtk_dialog_run (GTK_DIALOG (chooser));
    gtk_widget_destroy (chooser);
    return 0;
}
Comment 1 Federico Mena Quintero 2005-02-18 16:44:19 UTC
Vektor, could you please see the duplicate bug and get the strace logs that are
mentioned in its last comments?

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