[dolphin] [Bug 457151] New: Filenames that have improper (non-UTF-8) characters are anathema to dolphin

David Tonhofer bugzilla_noreply at kde.org
Tue Jul 26 09:35:58 BST 2022


https://bugs.kde.org/show_bug.cgi?id=457151

            Bug ID: 457151
           Summary: Filenames that have improper (non-UTF-8) characters
                    are anathema to dolphin
           Product: dolphin
           Version: 22.04.1
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: bughunt at gluino.name
                CC: kfm-devel at kde.org
  Target Milestone: ---

Created attachment 150916
  --> https://bugs.kde.org/attachment.cgi?id=150916&action=edit
The improperly named file in Dolphin

I used to have a few files apparently from an old archive with characters that
were not properly encoded as UTF-8, instead the bytestring for the filename was
ISO-8859-1. So for example "ü" would be encoded as 0xFC or octal 374.

I found out that it was impossible to rename to from inside Dolphin.

For example, if you create a file "FührerCat.txt" with the ü encoded as 0xFC
from the shell:

-----
$ mkdir TEST && cd TEST
$ touch $'F\xFChrerCat.txt'
$ ls
'F'$'\374''hrerCat.txt'
-----

Then the file is shown in dolphin with a placeholder (see attachment) but you
cannot rename it. Dolphin says "the file does not exist" and refuses to rename
it.

I have renamed them from the command line but somehow a few ended up in the
Trash, too (which can be done by moving their containing folder into the
trash).

In .local/share/Trash:

-----
$ cd .local/share/Trash/
$ tree
.
├── directorysizes
├── files
│   └── TEST
│       └── F\374hrerCat.txt
└── info
    └── TEST.trashinfo

3 directories, 3 files
-----


If one now attempts to empty the trash from Dolphin, Dolphin complains "could
not remove folder" so one has to do it from the command line

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list