Description of problem: I attempted to open a ZIP file in Krusader. This happens reproducibly lately, must be caused by a relatively recent (at most 1 month) update. Version-Release number of selected component: kf5-kio-core-5.96.0-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.krusader-6348c69ef69348f2b9075f150f3c8782.scope cmdline: /usr/libexec/kf5/kioslave5 /usr/lib64/qt5/plugins/kio_krarc.so krarc "" local:/run/user/1000/krusaderflLTzd.6.slave-socket crash_function: std::__atomic_base<QThreadData*>::load executable: /usr/libexec/kf5/kioslave5 journald_cursor: s=6e3a9538623b440298b267345bec80ed;i=2ac2c;b=35b3a8d8239f437da65bf548063440fe;m=5ac189b39;t=5e55367219dbd;x=1adf4c044da0af9e kernel: 5.18.13-200.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 std::__atomic_base<QThreadData*>::load at /usr/include/c++/12/bits/atomic_base.h:818 #1 std::atomic<QThreadData*>::load at /usr/include/c++/12/atomic:579 #2 QAtomicOps<QThreadData*>::loadRelaxed<QThreadData*> at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #3 QBasicAtomicPointer<QThreadData>::loadRelaxed at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 #4 QObject::thread at kernel/qobject.cpp:1487 #5 KIO::SlaveBase::SlaveBase at /usr/src/debug/kf5-kio-5.96.0-1.fc36.x86_64/src/core/slavebase.cpp:266 #6 kio_krarcProtocol::kio_krarcProtocol at /usr/src/debug/krusader-2.7.2-6.fc36.x86_64/krArc/krarc.cpp:144 #7 kdemain at /usr/src/debug/krusader-2.7.2-6.fc36.x86_64/krArc/krarc.cpp:129
Created attachment 1903235 [details] File: backtrace
Created attachment 1903237 [details] File: core_backtrace
Created attachment 1903238 [details] File: cpuinfo
Created attachment 1903239 [details] File: dso_list
Created attachment 1903240 [details] File: environ
Created attachment 1903241 [details] File: exploitable
Created attachment 1903242 [details] File: limits
Created attachment 1903243 [details] File: maps
Created attachment 1903244 [details] File: mountinfo
Created attachment 1903245 [details] File: open_fds
Created attachment 1903246 [details] File: proc_pid_status
Judging from the backtrace, this is a regression from https://invent.kde.org/frameworks/kio/-/commit/865d9b7a80a02979d46bf3dede2dc4d551d501ba – the possibility that `qApp` might be null is not considered here.
Thank you for the backtrace. I have added it to the upstream bug https://bugs.kde.org/show_bug.cgi?id=456348 and linked the bugs. I have also added a commit comment to the offending line linking to the bug report.
Similar problem has been detected: I clicked on a zip file in Dolphin. It seems to happen every time. Compressed tar files open just fine. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.dolphin-1a704ee05b4346128bc03195c418f12e.scope cmdline: /usr/libexec/kf5/kioslave5 /usr/lib64/qt5/plugins/kio_krarc.so krarc "" local:/run/user/1000/dolphinUTZSwP.46.slave-socket crash_function: std::__atomic_base<QThreadData*>::load executable: /usr/libexec/kf5/kioslave5 journald_cursor: s=0ffce1d568714dcba54f28466054ef92;i=b34ce;b=1ed03900214745bfa6dd4ed03a004a72;m=25990949c4;t=5ed09c02c4eaa;x=6aaf40eeeeee50e5 kernel: 6.0.5-200.fc36.x86_64 package: kf5-kio-core-5.99.0-1.fc36 reason: kioslave5 killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.