Opened 11 years ago
Last modified 11 years ago
#9390 new Bug report
Client confused trying to rename local file
Reported by: | Jerry Schwartz | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | rename, memory, local | Cc: | |
Component version: | Operating system type: | Windows | |
Operating system version: | 8.1 |
Description
Windows 8.1 Pro 64-bit
AMD Phenom 9750 quad core processor 2.8GHz
The client is not at this time connected to a server, but
it had been. The right window still shows the contents of the remote
server's directory; the left window shows the contents of the
current local directory. I have not refreshed either.
The local directory contains a single file, and I have verified its
name using Windows Explorer. The file name is 201404_bulletin.pdf.
When I try to rename the local file from 201404_bulletin.pdf to
latest-bulletin.pdf, Filezilla client pops up a Windows dialog box
that says
There is not enough memory to complete this operation.
2014_03_28
Date created 3/28/2014 7:24 PM
The box does not offer any more details.
There is no file with the name 2014_03_28. That is, in fact, the name
of the containing directory. I am positive that I am selecting the
file, not the directory.
Client information:
FileZilla Client
Version: 3.8.0
Build information:
Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2014-03-28
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions
Linked against:
wxWidgets: 2.8.12
GnuTLS: 3.2.12
SQLite: 3.7.16.2
Operating system:
Name: Windows NT 6.3 (build 9600)
Version: 6.3
Platform: 64 bit system
Attachments (3)
Change History (6)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Status: | new → moreinfo |
---|
Please attach a screenshot showing the error message.
by , 11 years ago
by , 11 years ago
Attachment: | Rename.gif added |
---|
by , 11 years ago
Attachment: | ErrorMessage.gif added |
---|
comment:3 by , 11 years ago
Status: | moreinfo → new |
---|
After refreshing the client's directory view, the problem persists.