Bug 290786 - Cannot rename files when filename encoding is broken
Summary: Cannot rename files when filename encoding is broken
Status: RESOLVED DUPLICATE of bug 165044
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-06 11:11 UTC by Martin Runge
Modified: 2012-01-06 12:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
You can select the file with broken filename and give it a new name, but rename will fail. (68.58 KB, image/png)
2012-01-06 11:11 UTC, Martin Runge
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Runge 2012-01-06 11:11:45 UTC
Created attachment 67505 [details]
You can select the file with broken filename and give it a new name, but rename will fail.

Version:           4.7 (using KDE 4.7.4) 
OS:                Linux

When a filename contains invalid characters because of wrong encoding, it is not possible to rename these files in the KDE File Open dialog or a filemanager like dolphin.


Reproducible: Always

Steps to Reproduce:
1. Create a file and break its filename's encoding:

> touch äöü.txt
> ls
äöü.txt
> convmv -f utf8 -t iso8859-1 --notest  äöü.txt
> ls 
???.txt

2. Try to rename that file with any KDE application.

Actual Results:  
E.g. KDE File dialog -> properties -> change filename back to äöü.txt (or any other filename without non ascii chars) will fail with the message: "no such file '???.txt'"

Dolphin fails, too.

Expected Results:  
It should be possible to rename all files that are displayed and are selectable.
It works with mc.
In the shell it is difficult to name the file with broken filename, but if you can specify a wildcard that expands to a single name it works: 

mv *.txt äöü.txt   # works as long as *.txt expands to a single file.
Comment 1 Jekyll Wu 2012-01-06 12:46:00 UTC
I think this is the same issue as bug 165044. Also see bug 204768.

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