Bug 457151 - Filenames that have improper (non-UTF-8) characters are anathema to dolphin
Summary: Filenames that have improper (non-UTF-8) characters are anathema to dolphin
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.04.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-26 08:35 UTC by David Tonhofer
Modified: 2023-03-07 09:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
The improperly named file in Dolphin (8.17 KB, image/png)
2022-07-26 08:35 UTC, David Tonhofer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Tonhofer 2022-07-26 08:35:58 UTC
Created attachment 150916 [details]
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
Comment 1 Mors Mortium 2023-03-07 09:04:45 UTC
Can confirm, moving, trashing and deleting (shift delete) don't work either. Another symptom was having a file named ''$'\200' and another named ''$'\362', and trying to rename one began renaming the other.