selecting files in the recently used category lead to incorrect filenames to be used

Bug #352105 reported by touristguy87
4
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Medium
gtk+2.0 (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

Hi, I have to report a HUUUUUUGE monster bug in
Nautilus 2.24.1
Ubuntu 8.10 up to date as of 3/30/09

with regards to saving an image.

the problem is that it will happily overwrite an image even if the "user" tells it to save the image with a different name, IF the target file was original selected from the "recent files" list.

Try this.

1-View a page on the web that has a jpeg, thusly:

http://www.flickr.com/photos/focusman55/3398649768/

2-right-click on the image, save it to your desktop.

3-find the image on the desktop, double-click it, it will open in a viewer. Close the image. The image should now be at the top of the "recent documents" list. Check this by going to the places menu and then "recent-documents", the top entry should open to the same image.

4-save the image (or any other image) again, the same way, but this time in the "save image" dialog click on "recently used" in the left part and click on the top entry in the list, on the right side. You should see the picture on the right (in a thumbnail viewer) and the filename at the very top in the file-box. Click on the name and *change the name* in the filename dialogbox, then hit alt-s to save the file with that name.

Right?

Wrong.

You just overwrote the original image, that you clicked on in the "recent documents" list.

Try it again, this time using the "desktop' link on the left side, then clicking on the image-file, then changing the name in the "filename" dialog. Hit alt-s or save. Now you have a new file with that name containing the image that you want to save.

As long as you select an entry in the "recently used" file list just before saving, you will overwrite that file, regardless of whatever you have set the "filename" dialog to. Not only will it save the file with that name regardless of whatever you put in, it will save it in that *directory* (which was the point of my using the "recently used" list in the first place).

How's that for a quick & easy way to lose a few days worth of work?

affects: ubuntu → gtk+2.0 (Ubuntu)
summary: - file save-as bug in Nautilus 2.24.1
+ recently changed doesn't respect the filename entered and overwrite
+ recent files rather
summary: - recently changed doesn't respect the filename entered and overwrite
- recent files rather
+ selecting files in the recently used category lead to incorrect
+ filenames to be used
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=577415

Changed in gtk+2.0 (Ubuntu):
assignee: nobody → desktop-bugs
importance: Undecided → High
status: New → Triaged
Changed in gtk:
status: Unknown → New
Revision history for this message
touristguy87 (touristguy87) wrote :

muchas gracias

Changed in gtk:
importance: Unknown → Medium
Revision history for this message
touristguy87 (touristguy87) wrote :

"summary: - recently changed doesn't respect the filename entered and overwrite
- recent files rather
+ selecting files in the recently used category lead to incorrect
+ filenames to be used "

No

On file save after clicking on an entry in the RU list, the app ignores the "name" field and just replaces the file selected from the RU list.

A-It should save the file with the name in the name field but in the directory with the file selected from the recently-used list.

B-It should never overwrite a file without a prompt/approval sequence.

Changed in gtk:
status: New → Fix Released
Revision history for this message
Mörgæs (moergaes) wrote :

Closing as the bug is marked 'fixed' upstream.
If a similar problem appears in the latest Ubuntu release please open a new report.

Changed in gtk+2.0 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.