Summary: | Dolphin can not access files named with special characters in a samba share | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | Victor Suarez <victorjss> |
Component: | kioslave | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | finex, mmenaz, victorjss, yzhernand |
Priority: | NOR | ||
Version: | 4.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Victor Suarez
2008-09-01 21:44:56 UTC
Not just with ñ, accented characters in spanish, just happens with files that have any characters in other languages like japanese. Reporting here just to put my +1 since i changed file manager and all is working again here, but dolplhin/konkeror/KDE 4.1.1 is still buggy in this aspect. (and not usable by anyone that uses these characters combinated with a-z letters and numbers) J. I'had a GNU/Linux box with samba and unix charset = ISO8859-15 encoding. I recently transferred all those files in GNU/Linux filesystem UTF8 with rsync. Now when Dolphin encounters those files (normal access, not through samba, they are local files) with accents and special characters in the name, shows a white "?" on black background. If I try to rename those files, happens as the bug reporter states ("The file xxx does not exist"). In addition, opening the old host directory with smb:// makes Dolphin block with the error "The process for the smb://192.168.1.3 protocol died unexpectedly" Bug is still present in the new KDE 4.1.2. *** This bug has been confirmed by popular vote. *** Weird, but with the same version of KDE (4.1.2), Kubuntu 8.10 does not suffer this problem. So this could be a distribution problem and not Dolphin problem. Not sure if this is related, but I experience this issue with folders with the character 1/2 (½) which shows up as a ? in a black diamond (�) in dolphin, konqueror, and konsole. I am using KDE 4.1.3 in Kubuntu Intrepid. I have seen this bug I believe since 4.0 but thought it was fixed. I had no problems in KDE 3. *** This bug has been marked as a duplicate of bug 158639 *** |