GNOME Bugzilla – Bug 516714
"Save all" not working in current folder
Last modified: 2010-08-30 06:27:46 UTC
Please describe the problem: I get an email with 5 pictures (attachments) and i want to save all 5 by clicking the "Save all" button. If I create a new folder and then click the "Save all" button I'm okay, i have the pictures saved in that new folder. But if i click the "Save all" button and just want to save the pictures in the current location I'm unable to save them by clicking on the "Save" button. I can just click the button on and on and the pictures are not saved. The Save dialog window is just sitting there and i have to go one folder back and then go forward to my previous folder so that i can save them (this is the workaround). Steps to reproduce: 1. Send yourself an email with 5 attachments. 2. Click on the "Save all" button and try to save them in the current location by clicking on the "Save" button in the Save dialog window. Actual results: Nothing. Expected results: The attachments should be saved in the current directory. Does this happen every time? Yes Other information: I've found some bugs similar to this one, but none of them contained all of the right details. If there's something i've missed please mark this as a duplicate. Thanks.
I think this is more of a GTK issue because I see the same thing when trying to use other GNOME applications. Particularly when using File Roller to extract a tarball or zip file to the current directory.
Looks like you're right. I have the same problem with GNOME 2.22 with other GTK apps as well. I ll name a few: Evolution, Deluge, File-roller. I have to actually click on Desktop in the left side pane to save the stuff i want there, even though I'm already at that location when the save dialog opens.
I hope i moved this to the right queue, if not please push it wherever it needs to go. Thank you.
I can confirm this. It happens when the focus is on the location entry in the file chooser dialog and the location entry is empty and the file chooser mode is set to ACTION_OPEN or ACTION_SELECT_FOLDER. In this case when pressing the 'action' button (like 'Extract' in case of file-roller, or 'Save' in case of mail attachments, or 'Open' in case of eog, or however the action button is configured) nothing will happen. What I think should happen is that the file chooser should fall-back to the file list (when the location entry is empty and focus is on location entry). This is possible as the file list is always available when the location entry is visible. See also related bug report for file-roller: http://bugzilla.gnome.org/show_bug.cgi?id=556376
Created attachment 125120 [details] [review] File chooser (location focus) open file/open folder fix
This bug has been present for a long time, much more than a year, and is indeed frustrating, especially with file-roller and email programs. It would be great for this to be fixed finally. I see the patch for it; can someone provide a status report? Thanks, Silas
*** Bug 582574 has been marked as a duplicate of this bug. ***
Note that there are several other issues with activation in select-folder mode that should be fixed at the same time. 1) open file chooser. Use pathbar to go up one directory. Now the initial folders name is in the entry, and it has focus. Press enter. You get an error dialog saying that the folder could not be created. WTF ? 2) Do the same as above, but then append a / to the entry contents before pressing enter. Now it works. 3) Try to trick the file chooser by entering . in the entry and pressing enter. Again you are greeted by the "Could not create directory" dialog. 4) Open the file chooser again and enter 'quququq' or somesuch. Press enter. Surprisingly, the folder is created.
*** Bug 590409 has been marked as a duplicate of this bug. ***
*** Bug 556376 has been marked as a duplicate of this bug. ***
Is this fixed? As per: http://git.gnome.org/browse/gtk+/commit/?id=b6d9bb6e1e6e916fc2ef25f5729b30ba91979597
I cannot reproduce the behavior on Evolution 2.28.3. It seems to be working.
I ll be closing the bug, since the main issue seems to be fixed. Please feel free to open another bug for anything related or re-open this one if you thing something is missing. Thanks guys.