Bug 167097 - Dolphin can't manipulate files that have names incorrectly encoded
Summary: Dolphin can't manipulate files that have names incorrectly encoded
Status: RESOLVED DUPLICATE of bug 165044
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-20 20:47 UTC by Marcelo Sales
Modified: 2008-12-20 12:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Files with invalid characters in their names can not be accessed in Dolphin (11.65 KB, image/png)
2008-07-20 20:48 UTC, Marcelo Sales
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcelo Sales 2008-07-20 20:47:05 UTC
Version:            (using KDE 4.0.98)
Installed from:    Fedora RPMs
OS:                Linux

If there are files with names incorrectly encoded in a directory, Dolphin is not able to move/copy/delete/rename them.
See the attached screenshots.
The files shown in it were in a tarball, probably created in a computer with a different filesystem encoding. Now it was uncompressed at my computer, I can't get rid of them, unless I open a konsole and use the command line to remove the directory in which the files are.
Konsole is able to acess the files and I can rename/delete/move/copy them from there. In this specific case shown in the screenshot, however, the file names are identical until the first invalid character, so I can't access them individually even in konsole (but I can remove the directory. In Dolphin, I can't do that either).
Comment 1 Marcelo Sales 2008-07-20 20:48:00 UTC
Created attachment 26288 [details]
Files with invalid characters in their names can not be accessed in Dolphin
Comment 2 Dario Andres 2008-08-27 19:52:42 UTC
This seems to be related to bug 160072 ( and therefore bug 159241 / bug 165400 / bug 165044 )
Comment 3 FiNeX 2008-12-20 12:39:07 UTC
I agree with Dario. I'm marking this as a dup of bug #165044 (which is temporary closed).

I've asked to reopen #165044 until is not fixed.

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