Bug 340950

Summary: With plasma 5, kdebase-dolphin 4.14.2 cannot delete files whose names contain Chinese
Product: [Frameworks and Libraries] kio Reporter: Jiehong <email>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED FIXED    
Severity: major CC: frank78ac, mail, nate, newbeewan, simonandric5
Priority: NOR    
Version: 4.14.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jiehong 2014-11-14 08:24:15 UTC
When trying to delete a file whose name contains Chinese characters, Dolphin says this file or directory does not exist.

Reproducible: Always

Steps to Reproduce:
1. Use dolphin 4.14.2 under plasma 5
2. Create a new text file with the following name: 中文.txt
3. Select your newly created file, and move it to trash with the contextual menu (or with del from your keyboard).

Actual Results:  
A window appears, with the following message:
"The file or folder /home/user/path/中文.txt does not exist."

Expected Results:  
The file should be able to be moved to the bin.

It may not be a dolphin bug by itself, but maybe plasma 5 does not set a UTF-8 locale by default? There is nothing related to UTF-8 in the Regional settings, which are set as following:
Region: United Kingdom - UK English (en_GB)

I've set it to Major, because it is simply broken for anyone in Asia potentially, and it does not allow one to delete files with dolphin.
Comment 1 Frank Reininghaus 2014-11-16 18:35:34 UTC
Thanks for the bug report. The KIO framework is responsible for deleting files, so I'll reassign. I don't know if the problem really is in KIO or somewhere else though.
Comment 2 newbeewan 2015-11-01 19:38:57 UTC
I have the same problem but with french UTF8 and fish as sftp client...

Is there any workaround ?

Regards
Comment 3 Julian Steinmann 2018-02-13 21:50:46 UTC
I can no longer reproduce the bug when following the steps from Jiehong with Dolphin 17.12.2. I guess that this is related to #344998. Both can now be closed, as the cause was most likely a problem in the Qt5 transition which is now completed.