Bug 392317

Summary:	Dolphin cannot handle files with non-UTF8 characters in its name
Product:	[Frameworks and Libraries] frameworks-kio	Reporter:	Eduardo Sánchez Muñoz <eduardosanchezmunoz>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	christoph, elvis.angelaccio, gabravier, kde, kdelibs-bugs
Priority:	NOR
Version:	5.44.0
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Eduardo Sánchez Muñoz 2018-03-25 17:02:05 UTC

If you create a file or directory with an non-UTF8 name (for example, with touch test$'\341'), Dolphin will show it in directory listings with an unicode replacement character (�), but it will not be able to handle the file in any other way, such as renaming, deleting or opening it.

Comment 1 Eduardo Sánchez Muñoz 2018-03-25 17:08:18 UTC

I forgot to say that Dolphin will just say that the file does not exist.

Comment 2 Kai Uwe Broulik 2018-03-26 08:05:32 UTC

Looks like a bug in KIO, the same also happens in file dialog

Comment 3 Kai Uwe Broulik 2018-03-26 08:08:31 UTC

In KRun it fails in

const QString localPath = d->m_strURL.toLocalFile();
        if (!QFile::exists(localPath)) {

Perhaps somewhere it actually replaces the broken unicode character by the replacement character, losing the original character, and then the file names don't match up and it aborts

Comment 4 Christoph Feck 2018-03-26 12:28:54 UTC

This is bug 165044.

Comment 5 Christoph Cullmann 2024-06-24 20:01:38 UTC


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