Can't enter into iso images if path contains symlinked direcories. Showing an error "file or folder does not exist". Maybe kio_iso bug. See also old discussion at https://groups.google.com/forum/#!topic/krusader-devel/OnrMQzFPgPQ Same file opens fine if path does't contain any symlink. Reproducible: Always
Can't reproduce this problem. I did: $ cd $ ln -s ~/laptop/software/cd isos where ~/laptop is a nfs/sshfs mount to my ~ on the laptop; I can browse sanely any iso. Can you confirm you are using the git version of krusader? There are still no packages for krusader git version in kubuntu. I tested with 2.4.0b3 version too and it works fine.
(In reply to Davide Gianforte from comment #1) > Can't reproduce this problem. I did: > > $ cd > $ ln -s ~/laptop/software/cd isos > > where ~/laptop is a nfs/sshfs mount to my ~ on the laptop; I can browse > sanely any iso. > > Can you confirm you are using the git version of krusader? There are still > no packages for krusader git version in kubuntu. I tested with 2.4.0b3 > version too and it works fine. Yes, I compiled it to /opt/krusader directory and launch it from there. Can't test the latest version of Krusader because I still use KDE 4 (it requires Plasma 5 now). I just found out that this bug affects relative symlinks only. Links with full path have no problem.
Found out that this bug affects relative symlinks only. Links with full path have no problem.
Confirmed using cd work ln -s ../software/iso isos files inside work/isos can't be browsed
Can confirm under Plasma 5 for kio_iso 2.6.0-2.1 from openSUSE Tumbleweed. Absolute symlinks work, relative don't.
Confirmed on v2.7.0.
Created attachment 121506 [details] KrDebug Using the integrated debugger, I found that the plugin is called without the filename when the symlink is relative ("iso"), the filename is complete when the symlink is absolute ("iso2"). This require some KIO investigation.