Registered Member
|
Something is not working as it used to - Krusader opens iso-files with Ark instead of entering into them like in a directory.
I am running Krusader 2.5.0 on KDE Frameworks 5.26.0 on Qt 5.6.1 and the xcb windowing system, all on a newly installed Gecko KDE Static edition 422.161228.0 When I ran Krusader 2.4.0 on openSUSE LEAP 41.2 , Krusader entered an iso-file when I pressed enter on it. kio-slave for iso is installed, and the protocol file /usr/share/kservices5/iso.protocol is readable.
I have tried reinstalling kio_iso to no avail. Dolphin opens iso-files with Ark too, and Ark is associated with the x-cd-image filetype. I tried removing this association, but when I put the cursor on an iso-file as the current one and pressed enter, Krusader asked for which program to use for opening the iso-file. So, what am I doing wrong, and how can I correct it? |
Registered Member
|
An ISO is a single file, a compressed file, similar to a ZIP file. It is not a directory and has no directory structure. It has to be "unpacked" before you can see what's in it.
File managers cannot "open" an ISO, which is why they are offering to unpack it with Ark or process it with a disc burning tool such as K3b. Not sure what you're trying to do with an ISO file.
The Town Site Buy your own town and promote it however you want.
|
Registered Member
|
@Cobber
Krusader has it's own "iso" KIO slave protocol for opening ISO files like "zip" does for archives. @freddyvejen Try this: In Krusader settings->Archives->"Browse archives as folder" must be checked. Alternative way is right-click on iso file and select "Browse archive". |
Registered Member
|
|
Registered Member
|
Thank you abika
> Try this: In Krusader settings->Archives->"Browse archives as folder" must be checked. It was already checked. I tested setting it on and off and restarting Krusader in between, and it didn't affect the behaviour for iso-files, but it did for zip-files. > Alternative way is right-click on iso file and select "Browse archive". Yes, that works. Thank you. |
Registered Member
|
I tested this now with 2.5.0 (I usually use a developer build) and can confirm the buggy behaviour you have. But this is already fixed in the code and will be in the next release. |
Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]