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 166773 - Filename edit mode terminates when directory contents are updated
Filename edit mode terminates when directory contents are updated
Status: RESOLVED DUPLICATE of bug 87701
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.8.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-09 12:09 UTC by Alexander “weej” Jones
Modified: 2005-02-12 07:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Alexander “weej” Jones 2005-02-09 12:09:41 UTC
Please describe the problem:
I was downloading a file into a folder while trying to rename another. Every 
time I tried to change the name the view would seem to refresh with a new file 
size for the currently downloading file, making it impossible to rename the 
file without moving it out of the current directory first.

This is in List View

Steps to reproduce:
1. Activate List View in a new folder
2. Create an empty file inside the folder
3. Start downloading a new file into the folder
4. Attempt to rename the first empty file

Actual results:
Edit mode is activated, but then it exits when the filesize is updated for the 
downloading file.

Expected results:
Edit mode remains activated so I can type a new filename.

Does this happen every time?
Yes

Other information:
I have not tested this with Icon View. I will report my findings later.

Thanks
Comment 1 Alexander “weej” Jones 2005-02-09 15:55:00 UTC
No problems with Icon View as far as I can see.
Comment 2 Martin Wehner 2005-02-12 07:38:35 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

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