Someone had reported that viewing archives as folders does not work in Krusader: *.zip archives appear empty, *.tar.* are opened with external program, and only *.7z are displayed correctly. I've glanced at the sources, and see this: listCmd << fullPathName("unzip") << "-ZTs-z-t-h"; These options are not compatible with our native unzip(1), they are for Info-ZIP implementation. This had been reported upstream (linked URL).
Installing the kio-extras package solves the problem.
(In reply to Vurefozu from comment #1) > Installing the kio-extras package solves the problem. Exactly which one? There were two: 1) *.zip archives appeared empty, and 2) *.tar.* being opened with external program. Also, it's still unclear why installing it fixes anything, we need in-depth analysis before we can commit a proper fix.
> 1) *.zip archives appeared empty Solution to the problem: /usr/bin/unzip replaced by /usr/local/bin/unzip > 2) *.tar.* being opened with an external program. Solution to the problem: pkg install kio-extras Also, kio-extras adds SFTP functionality to krusader. The only thing that doesn't open as a directory is *.tar.lzma archives Even after installing the "lzma" package and replacing /usr/bin/lzma on /usr/local/bin/lzma
(In reply to Vurefozu from comment #3) I looked into switching krusader to use the ${LOCALBASE} binary, e.g. here [1] [1] https://invent.kde.org/utilities/krusader/-/blob/master/app/Archive/krarchandler.cpp
(In reply to Vurefozu from comment #3) > Solution to the [*.tar.*] problem: > pkg install kio-extras > Also, kio-extras adds SFTP functionality to krusader. I'd still like to see in the code how exactly Krusader breaks without it, does it emit any warning? Just to be sure that `devel/kio-extras' is indeed what's needed, not some dependency it pulls.
(In reply to Alexey Dokuchaev from comment #5) > I'd still like to see in the code how exactly Krusader breaks without it, does it emit any warning? I will not answer the question, it is necessary to ask the developers of krusader.
(In reply to Vurefozu from comment #6) > I will not answer the question, it is necessary to ask the developers of > Krusader. Right, what I meant is that whoever committing a fix should have sufficient domain knowledge and KDE/C++ experience to make proper judgement.