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 473981 - Create folder first creates `untitled folder' and then renames it
Create folder first creates `untitled folder' and then renames it
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.18.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-05 18:16 UTC by David Benjamin
Modified: 2016-09-06 08:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description David Benjamin 2007-09-05 18:16:26 UTC
Please describe the problem:
When one creates a folder in Nautilus, it first creates a folder and then renames it, as opposed to waiting for the user to supply a name and then creating a folder with the correct name.

This is particularly annoying when connecting to a network server with very high latency; it adds an extra wait because now we perform two actions instead of one.

Steps to reproduce:
1. Connect to a (preferably slow) FTP server
2. Create a new folder
3. Give it some name
4. Press enter


Actual results:
There is a long pause after steps 2 and 4.

Expected results:
Step 2 should be instant; there is no reason to actually create `untitled folder'. (4 understandably causes a pause since the network is slow.)

Does this happen every time?
Yes

Other information:
This also causes the additional oddity that, if you have two views of the same directory open (using browser mode since spatial does not allow that, to the best of my knowledge.... or using some other file-manager or whatever), you will see a random `untitled folder' appear that, while not confusing, seems extremely pointless.
Comment 1 Sebastien Bacher 2009-04-15 20:41:06 UTC
There is a similar issue described on https://bugs.launchpad.net/bugs/302977
Comment 2 Alexandre Franke 2016-09-06 08:44:19 UTC
That should be fixed with the new dialog in 3.18.