Description of problem: nautilus can't create "unamed folder X", if it exist on the sftp target. Version-Release number of selected component (if applicable): nautilus-extensions-2.26.3-1.fc11.x86_64 nautilus-2.26.3-1.fc11.x86_64 not sure if someone here is involved: gvfs-archive-1.2.3-8.fc11.x86_64 gnome-vfs2-2.24.1-2.fc11.x86_64 gvfs-obexftp-1.2.3-8.fc11.x86_64 gvfs-gphoto2-1.2.3-8.fc11.x86_64 gnome-vfsmm26-2.26.0-1.fc11.x86_64 gnome-python2-gnomevfs-2.26.1-1.fc11.x86_64 gvfs-1.2.3-8.fc11.x86_64 gvfs-smb-1.2.3-8.fc11.x86_64 gvfs-fuse-1.2.3-8.fc11.x86_64 How reproducible: Always Steps to Reproduce: 1. connect to a remote ssh server via sftp 2. right click to create a new folder and leave its default name 3. right click again to create another folder Actual results: step2: nautilus sucessfully creates a new "unnamed folder" step3: nautilus failed to create a new "unnamed folder 2" with "unknown reason" Expected results: nautilus creates a another folder and adds a suffix number behind it. Additional info: On local filesystem it works fine. nautilus adds 1,2,3 on so on to new "unnamed folders" It may be, that only !english installations affected? For me the "unnamed folder" becomes "Namenloser Ordner". (de_DE.UTF-8) best regards
Confirming for sftp, other protocols seem to be fine (ftp, smb, dav). English locale here.
gvfs-1.2.3-11.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/gvfs-1.2.3-11.fc11
gvfs-1.2.3-11.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.