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 587579 - Can't open the previously chosen directory
Can't open the previously chosen directory
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2009-07-02 08:21 UTC by Przemyslaw Wesolek
Modified: 2018-02-10 03:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Przemyslaw Wesolek 2009-07-02 08:21:15 UTC
In some applications (Thunderbird, file-roller) I'm asked to choose a directory to perform an operation on (save all attachments, extract). When I just want to accept the last directory, which is pre-chosen and displayed in file dialog, the "Open" (or "Extract") button does nothing.

Only when I click on "Bookmarks" pane or directory contents pane, the button becomes active and lets me choose the previous directory.

This behavior is a little annoying, especially when working with keyboard only -- there's no way not to use a mouse.
Comment 1 Kaial 2009-07-13 10:20:27 UTC
Same problem. Also, if you enter a subdirectory, return back to its parent and click «Open», subdirectory will be chosen instead of the current directory. If you click on empty space under subdirectories list, it will change nothing. If you will enter «.» in Location field, it will change nothing. Only way to select current directory is to go to up once again and choose our directory as subdirectory.
Comment 2 Matthias Clasen 2018-02-10 03:45:53 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.