GNOME Bugzilla – Bug 325749
GTKFileDialog says any file already exists if trying to save in GIMP
Last modified: 2006-01-11 10:04:19 UTC
Please describe the problem: When I try to "save as" any file in Gimp, the program says the file already exists. It seems the bug was introduced in gtk+-2.8.9. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
I can't reproduce this.
Me neither, using GTK 2.8.9 and GLib 2.8.5 exactly as distributed from ftp.gtk.org.
I have seen this but have not investigated any further.
Alexander, can you think of anything special about the situation where you get this? Anything special about the volume where this happens. Do you get it every time, whatever name file you try to save, wherever you try to save it? Is it a warning only, a dialog that asks whether you want to overwrite (even though you are sure no file with that name exists earlier), or an error message that aborts the saving?
File/Acquire/Paste as New File/Save as enter: d:\temp\nothere.png shows: A file named 'd:\temp\nothere.png' already exists. Do you want to replace it with the image you are saving? Nothing special with the partiton (NTFS).
Tor, just as Hans has said, nothing special. Trying to "save as" any file from any origin (opened existing file, pasted from the clipboard or grabbed screenshot) pop-ups the dialog : The file with the name'D:\Temp\09.01.06_to_print\Origins\PICT3246_10x15.JPG' exists... (In Russian, of course). Do you want to replace it? This is not an exception, this is a standard confirmation dialog of file replacement. If I confirm, the file is being saved without problems.
I'd deinstalled and installed the GTK+, but nothing has changed.
Hmm, this is with GIMP 2.3.x, right? With a rather old build of that I indeed see this, too. This presumably is a duplicate of bug #309729, which has been fixed already.
This happens with the latest public available build - 2.3.5. There is still no 2.3.6 build for Windows, so I cannot say anything on the last development build.
*** This bug has been marked as a duplicate of 309729 ***