https://bugs.kde.org/show_bug.cgi?id=451863
--- Comment #7 from Rafael Linux User <rafael.linux.u...@gmail.com> --- I can't test with an SFTP server because our servers are FTP servers managed by other teams. In any case, it's clear to me that to be secure or not has nothing to do with the problem. I'm not an expert on KDE libraries. The fact is that programs that (as I understand it) use kio-fuse (such as Dolphin and Krusader) are not able to access that folder. However, Caja (which I think uses Gnome libraries) does manage to access it, just as it happens from Windows with Filezilla and TotalCommander (as I mentioned in my first message). What else could be the cause of this behaviour of Dolphin and Krusader exclusively? Moreover, I have taken the trouble to install Filezilla on Plasma and try with it exactly the same access procedure to that folder. As expected, it accesses (after 10 or 15 seconds) that folder and displays its contents. I can only mention in this case, that Filezilla shows in the log the message: "Invalid character sequence received, UTF-8 is disabled. Select the UTF-8 option in the site manager to force UTF-8". However, Filezilla, instead of continuing to display the directory tree where the symbolic link is located, "jumps" to base path and displays the tree from which the original path to which the symbolic link points (/nfs/files) is hanging. Caja, on the other hand, does an impeccable job: Not only does it show the contents of the folder, but it also keeps showing the correct directory tree, without jumping to the path to which the symbolic link points. -- You are receiving this mail because: You are watching all bug changes.
