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 327289 - When saving files file requester always says "a file named <file> already exists" even if it doesn't.
When saving files file requester always says "a file named <file> already exi...
Status: RESOLVED DUPLICATE of bug 309729
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.8.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2006-01-17 07:18 UTC by muzh
Modified: 2006-02-15 07:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description muzh 2006-01-17 07:18:14 UTC
Please describe the problem:
Noted on Gimp- 2.3.5/gtk+-2.8.10 (glib-2.8.5).  "Save file as" -> navigate to where one wants 
to save file, enter a few characters -> files matching pattern shown.  Change filename to 
something not in directory, but still "A file named <new file name> already exists.  Do you 
want to replace it with the image you are saving?" pops up.   
Gimp-2.3.5/gtk+-2.8.7 behaved normally.  Upgrade to gtk-2.8.10 -> abnormal behaviour as 
described.  Recompile Gimp-2.3.6 against gtk-2.8.10 -> no change in abnormal behaviour. 

Steps to reproduce:
1. As above in Gimp. 
2.  
3.  
 

Actual results:
Keeps showing "File exists.  Do you want to replace it?"  But I can still save the file, "replacing" 
the non-existent file. 

Expected results:
As above.  Annoying in the extreme without being incapacitating. 

Does this happen every time?
Yes, since upgrading to glib-2.8.5 (from 2.8.4) and gtk-2.8.10 (from 2.8.7) 

Other information:
I think I have described it adequately.  Running kernel-2.6.12.5/glibc-2.3.6/gcc-4.0.2 (linux 
from scratch)
Comment 1 muzh 2006-02-06 02:53:28 UTC
This appears to be a duplicate of bug 309729 reported for GIMP
Funny I only got the spurious "File exists" error only after upgrading gtk+ from 2.8.7 to 2.8.10
Comment 2 muzh 2006-02-10 10:01:49 UTC
Upgrade GIMP from 2.3.6 to 2.3.7 seems to fix bug.  it is no longer present.
? because it uses new features of gtk-2.8.x
Comment 3 muzh 2006-02-15 07:07:09 UTC

*** This bug has been marked as a duplicate of 309729 ***