On two computers (both with Slackware-current64, kernel 4.4.1 glibc-2.22-x86_64) These computers connect to each other via ssh. comp1 has: dolphin15.12.1 Using: KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system comp2 has: dolphin4.14.13 KDE Platform 4.14.14 Wnen copying files from within comp1 (via drag and drop in dolphin) I get this error: "fish://......../filename cannot read file. Retry/Cancel" This happens if the remote filename(s) or folder name(s) have non latin1 characters. The remote files and folders with only latin characters in names are copied OK. This happens with Konqueror on kde5 as well. When copying files from within comp2 (kde4) everything works as expected, i.e. no problems with remote non latin filenames and they get copied (no error messages). Even when the remote files and folders reside on the kde5 computer. Reproducible: Always Steps to Reproduce: 1.When on kde5 open dolphin filemanagers. Split view and connect to a remote computer via ssh. 2.On the remote computer view one can see all files and folders, even those with non latin names. 3.Drag a file with a non latin name from the remote computer into a folder on the local (kde5) computer. The following error message is displayed: "fish://......../filename cannot read file. Retry/Cancel" and nothing gets copied. Actual Results: The following error message is displayed: "fish://......../filename cannot read file. Retry/Cancel" and nothing gets copied. Expected Results: The remote files and folders with non latin names should be copied over to the kde5 computer over kio-fish.
I can confirm this issue. (KF 5.19, Qt 5.5.1, Plasma 5.5.4) Also when copying such file or directory to remote location through fish protocol -> it actually creates name with question marks: 1) Copy file "čeněk.txt" to remote directory through fish 2) Observe that "?en?k.txt" is actually created -> this way the file can be read just fine I've tested this use-case also with sftp and ftp protocols and these are not affected by this issue.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!