Bug 457791 - Krusader does not open ISO files
Summary: Krusader does not open ISO files
Status: CONFIRMED
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: 2.8.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2022-08-12 09:30 UTC by empyreal
Modified: 2023-07-09 21:26 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description empyreal 2022-08-12 09:30:15 UTC
SUMMARY
Krusader do not open ISO files as archives. Can't view content of ISO image.

STEPS TO REPRODUCE
1. Find ISO file.
2. Press Enter key.

OBSERVED RESULT
No content or error displayed. Status >>Reading...

EXPECTED RESULT
Expect to see content of ISO image.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.10
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.4
Kernel Version: 5.15.0-46-generic (64-bit)
Graphics Platform: X11
Comment 1 empyreal 2022-08-12 10:50:27 UTC
Browse Archives As Folders selected.
Same situation on 2.8.0-dev version.
ISO files are located on NTFS drive.
Can browse ISOs with right menu Mount function.
Comment 2 Nikita Melnichenko 2022-08-14 08:24:58 UTC
Can you open ISO from a nix filesystem (ext, btrfs or other) and not from NTFS? It works for me on 2.8.0-dev version, I don't have NTFS to try at this moment.
Comment 3 empyreal 2022-08-14 09:31:18 UTC
Tried on ext4
No content or error displayed. Status >>Reading...
Comment 4 Nikita Melnichenko 2022-09-02 08:25:45 UTC
Does it happen with all the ISO on your end? Can you test on some public ISO (say, Ubuntu installer) and provide a link to the ISO file?
Comment 5 empyreal 2022-09-02 08:36:40 UTC
This happens with every ISO, regardless size, origin, whatever... kubuntu-22.04-desktop-amd64.iso https://kubuntu.org/getkubuntu/
Comment 6 Theo 2022-11-26 19:37:30 UTC
I can confirm the problem under openSUSE Tumbleweed, kio_iso version 2.99.40git560~e1988e9-122.1 [1]. Following Guidelines and HOWTOs [2], I find that kioslave5 aborts with a segmentation fault:

$ export KDE_SLAVE_DEBUG_WAIT=iso
$ krusader # press Enter on ISO image file
kioslave5: 'gdb kioslave5 16493' to debug
kioslave5: 'kill -SIGCONT 16493' to continue
$ gdb kioslave5 16493
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
QObject::thread (this=0x0) at kernel/qobject.cpp:1520
1520        return d_func()->threadData.loadRelaxed()->thread.loadAcquire();
(gdb) backtrace
#0  QObject::thread (this=0x0) at kernel/qobject.cpp:1520
#1  0x00007f6721935b87 in KIO::SlaveBase::SlaveBase (this=<optimized out>, protocol=..., pool_socket=..., app_socket=..., this=<optimized out>, protocol=..., 
    pool_socket=..., app_socket=...) at /usr/src/debug/kio-5.100.0/src/core/slavebase.cpp:266
#2  0x00007f6721a39c01 in kio_isoProtocol::kio_isoProtocol (app="local:/run/user/1000/krusaderJXESmB.2.slave-socket" = {...}, pool=<qt_array+24> "", 
    this=0x7ffd6b6611b0) at /usr/src/packages/BUILD/krusader-2.99.40git560~e1988e9/plugins/iso/iso.cpp:72
#3  kdemain (argc=<optimized out>, argv=<optimized out>) at /usr/src/packages/BUILD/krusader-2.99.40git560~e1988e9/plugins/iso/iso.cpp:50
#4  0x000055bbc8fbd370 in main (argc=5, argv=0x7ffd6b661418) at /usr/src/debug/kio-5.100.0/src/kioslave/kioslave.cpp:152

[1] https://build.opensuse.org/package/show/KDE:Unstable:Extra/krusader
[2] https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_IOSlaves
Comment 7 Nikita Melnichenko 2022-11-29 08:21:04 UTC
I can confirm this as well. It seems like it's related to a KIO update. Needs investigation.

For krarc we had a migration [1] from SlaveBase to WorkerBase. Maybe we need to have a similar one for the iso plugin. Adding Harald for his opinion.

[1] https://invent.kde.org/utilities/krusader/-/merge_requests/86
Comment 8 Yuri K 2023-07-09 21:26:55 UTC
Still happening, either on 2.8.0 or 2.7.2. Is this a KDE issue? If so, a corresponding bug report needs to be opened @ KDE.