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 326047 - Renaming files with (invalid unicode) string leaves that string at the entry.
Renaming files with (invalid unicode) string leaves that string at the entry.
Status: RESOLVED DUPLICATE of bug 103802
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.12.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-07 02:46 UTC by Alberto Ruiz
Modified: 2006-01-07 10:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Alberto Ruiz 2006-01-07 02:46:08 UTC
Please describe the problem:
I have an UTF8 linux enviroment, and I have files that have invalid characters
for that encoding so nautilus can't read the files' names properly.
When I edit the file to fix the character, the (invalid unicode) string still in
the editing entry, so I need to fix the character, and erase the " (invalid
unicode)" string at the end of the file.

Steps to reproduce:
1. Select a file with invalid unicode message
2. Press F2 or Right-Click->Rename



Actual results:
The " (invalid unicode)" string stills on the text of the entry to change the name.

Expected results:
The " (invalid unicode)" string shouldn't be there, I want to fix the original
string I think that nobody want to adds that string after fixing the bad
characters, so when you try to fix a lot of files (for example, the title of the
album in the mp3 files' titles it's repeated for every file, so I need to delete
the final string every time that I fix each string.

Does this happen every time?
Yes it does.

Other information:
Comment 1 Sebastien Bacher 2006-01-07 10:55:37 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 103802 ***