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 673780 - Populate file chooser on demand, not on create
Populate file chooser on demand, not on create
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2012-04-09 14:34 UTC by Jean-François Fortin Tam
Modified: 2018-04-15 00:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jean-François Fortin Tam 2012-04-09 14:34:13 UTC 
See also: https://bugzilla.redhat.com/show_bug.cgi?id=712945

If, for some reason, gvfs is "waiting" for a response from a network mount of some kind, Evolution will not be able to show the message composer window to reply/forward a message.

Now, I'd understand the filechooser blocking (kind of), but not the message composer window which shouldn't require this at all; I suppose it uses gvfs for the attachment bar, but that should not be synchroneous to the rest of the window, hence this bug report.
Comment 1 Milan Crha 2013-01-31 13:05:37 UTC 
Thanks for a bug report. After an observation what the GtkHTML editor does, I realized that it has most of its UI in a GtkBuilder's .ui file, thus there is not much to be done, because the GtkBuilder creates all the widgets from the .ui file. I believe the best option would be to teach GtkFileChooser(Button) to not populate itself immediately, but only on demand, when it's really needed (the preselected "None" value doesn't require to check mount points or whatever, user can wait when he/she clicks the button itself. I guess even the gtk_file_chooser_set_file/name() may not require the list of mounted points or a folder contents, but I do not know that code at all, thus maybe they require it for checking destination availability. Either way, that is not an issue for the .ui defined widget, because that is preselected with "None" anyway.
Comment 2 Matthias Clasen 2018-02-10 05:04:47 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 3 Matthias Clasen 2018-04-15 00:23:38 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