Bug 377172 - Dolphin unable to read open copy move files with some unicode characters
Summary: Dolphin unable to read open copy move files with some unicode characters
Status: RESOLVED NOT A BUG
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-03 16:38 UTC by Nathan Shearer
Modified: 2017-03-09 16:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
unicodegenerator.sh (151 bytes, application/x-shellscript)
2017-03-06 16:57 UTC, Nathan Shearer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Shearer 2017-03-03 16:38:04 UTC
Dolphin can't use files with some unicode files, often causing batch moves or copies to fail on my systems.

Use a terminal and create a file:
# touch filename_�_filename.txt

Then try to do anything with that file in Dolphin, it will show the file, but cannot interact with it.
Comment 1 Elvis Angelaccio 2017-03-05 17:43:23 UTC
Can you tell exectly which unicode characters don't work for you? My browser cannot render the one in your example.
Comment 2 Nathan Shearer 2017-03-06 16:57:05 UTC
Created attachment 104414 [details]
unicodegenerator.sh

I've attached a small shell script which will generate the first 256 unicode characters in a folder called files. I found that U+8A was the first of many that trigger this bug. The files exist on disk, but dolphin cannot interact with them.
Comment 3 Christoph Feck 2017-03-08 15:00:38 UTC
This shell scripts generates filenames that have invalid UTF-8 representation.
Comment 4 Nathan Shearer 2017-03-08 15:28:28 UTC
I switched the bug back to UNCONFIRMED (not sure if I should have set it to VERIFIED).

The shell script does create files with invalid UTF-8 representations, and such files do actually exist out there. I've often downloaded zip files, extracted them via the right-click dolphin 7z menu, then been unable to rename/move/copy the resulting folder because one of the files in it has an invalid representation.

Even though the file has an invalid UTF-8 string, it is still a valid filename and a real file on disk.
Comment 5 Christoph Feck 2017-03-09 02:53:34 UTC
Complain to Qt developers. I am not going through the discussion at bug 165044 again.
Comment 6 Nathan Shearer 2017-03-09 16:50:19 UTC
I've reported this bug upstream at https://bugreports.qt.io/browse/QTBUG-59402 and referenced this bug along with bug 165044 and https://marc.info/?l=kde-core-devel&m=122025063320264&w=2