Bug 452789

Summary: Krusader crashes when F3-viewing docx file
Product: [Applications] krusader Reporter: Erik Quaeghebeur <bugs.kde.org>
Component: generalAssignee: Krusader Bugs Distribution List <krusader-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: davide, krusader-bugs-null
Priority: NOR Keywords: drkonqi
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Erik Quaeghebeur 2022-04-20 09:17:01 UTC
Application: krusader (2.7.2 "Peace of Mind")
 (Compiled from sources)
Qt Version: 5.15.3
Frameworks Version: 5.90.0
Operating System: Linux 5.15.32-gentoo-r1-a x86_64
Windowing System: X11
Distribution: Gentoo/Linux
DrKonqi: 5.23.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I F3-viewed a docx file (by mistake, but still). Obviously, F3-viewing a binary file is usually not what you want, but for example pdf files just get opened in a KPart, this might also be done for other types. If no associated KPart exists, an error message or so should pop up. In any case, crashing is not the right thing to do.

- Other:
I remember that there was (still is) a bug that caused Krusader to crash when F3-viewing some compressed files. Given that docx files are actually zip files, this may be related.

The crash can be reproduced every time.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault

[KCrash Handler]
#4  0x00007a4fd4f61315 in std::__atomic_base<QObjectPrivate::ConnectionData*>::load (__m=<optimized out>, this=<optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/atomic_base.h:838
#5  std::atomic<QObjectPrivate::ConnectionData*>::load (__m=<optimized out>, this=<optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/atomic:570
#6  QAtomicOps<QObjectPrivate::ConnectionData*>::loadRelaxed<QObjectPrivate::ConnectionData*> (_q_value=...) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#7  QBasicAtomicPointer<QObjectPrivate::ConnectionData>::loadRelaxed (this=<optimized out>) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#8  QObjectPrivate::ensureConnectionData (this=<optimized out>) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject_p.h:377
#9  QObjectPrivate::addConnection (this=0x778cb83d7132bf51, signal=signal@entry=3, c=c@entry=0x57e5f73e22b0) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:324
#10 0x00007a4fd4f64196 in QObjectPrivate::connectImpl (sender=0x57e5f8132ff0, signal_index=3, receiver=0x57e5f8217730, slot=<optimized out>, slotObj=<optimized out>, type=<optimized out>, types=<optimized out>, senderMetaObject=<optimized out>) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.h:132
#11 0x00007a4fd4f6466d in QObject::connectImpl (sender=0x57e5f8132ff0, signal=<optimized out>, receiver=0x57e5f8217730, slot=0x7ffca3243000, slotObj=0x57e5f831bdd0, type=Qt::AutoConnection, types=0x0, senderMetaObject=0x7a4f62f8f960 <Kerfuffle::ReadOnlyArchiveInterface::staticMetaObject>) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:5001
#12 0x00007a4f62f38da4 in Kerfuffle::Job::connectToArchiveInterfaceSignals() () from /usr/lib64/libkerfuffle.so.21
#13 0x00007a4f62f3a3c7 in Kerfuffle::LoadJob::doWork() () from /usr/lib64/libkerfuffle.so.21
#14 0x00007a4fd4f65a16 in QObject::event (this=0x57e5f8217730, e=0x57e5f435bc10) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:1314
#15 0x00007a4fd593396f in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x57e5f8217730, e=0x57e5f435bc10) at /var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/src/widgets/kernel/qapplication.cpp:3637
#16 0x00007a4fd4f3a138 in QCoreApplication::notifyInternal2 (receiver=0x57e5f8217730, event=0x57e5f435bc10) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1064
#17 0x00007a4fd4f3d7a5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x57e5f36d4400) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1821
#18 0x00007a4fd4f8c853 in postEventSourceDispatch (s=0x57e5f37be010) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#19 0x00007a4fd374a16b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007a4fd374a428 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007a4fd374a4df in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007a4fd4f8c2e4 in QEventDispatcherGlib::processEvents (this=0x57e5f37c34d0, flags=...) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qeventdispatcher_glib.cpp:423
#23 0x00007a4fd4f38b2b in QEventLoop::exec (this=this@entry=0x7ffca3243470, flags=..., flags@entry=...) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x00007a4fd4f4115d in QCoreApplication::exec () at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x000057e5f17963d8 in ?? ()
#26 0x00007a4fd47fe2fa in ?? () from /lib64/libc.so.6
#27 0x00007a4fd47fe3a8 in __libc_start_main () from /lib64/libc.so.6
#28 0x000057e5f1797bfa in _start ()
[Inferior 1 (process 458951) detached]

Reported using DrKonqi
Comment 1 Davide Gianforte 2023-03-02 18:36:55 UTC
This bug was solved in the latest Krusader release (2.8.0). Can you manage to update to the latest version and check if the issue happens again?
Comment 2 Erik Quaeghebeur 2023-03-02 20:30:13 UTC
It does not happen anymore for me with 2.8.0.