Application: dolphin (22.04.3) Qt Version: 5.15.4 Frameworks Version: 5.97.0 Operating System: Linux 5.19.0-1-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux bookworm/sid DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I was browsing NFS folder and clicked sort by Modified, started scrolling. One second later Dolphin crashed. The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 0x00007fe9d1a3a83c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x00007fe9d19eea52 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x00007fe9d19d9469 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x00007fe9d1a2ec18 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x00007fe9d1ac9c62 in __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x00007fe9d1ac9c40 in __stack_chk_fail () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x00007fe9d3abb705 in KFileItem::overlays() const () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #11 0x00007fe9d40e8347 in KFileItemModelRolesUpdater::rolesData(KFileItem const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #12 0x00007fe9d40eb883 in KFileItemModelRolesUpdater::slotGotPreview(KFileItem const&, QPixmap const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #13 0x00007fe9d20b49af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007fe9d3d811d7 in KIO::PreviewJob::gotPreview(KFileItem const&, QPixmap const&) () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #15 0x00007fe9d3d8560b in ?? () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #16 0x00007fe9d3d8677a in ?? () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #17 0x00007fe9d20b49af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007fe9d3b27194 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #19 0x00007fe9d20b49af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00007fe9d3af8dd2 in KIO::SlaveInterface::data(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #21 0x00007fe9d3afb24a in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #22 0x00007fe9d3af9696 in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #23 0x00007fe9d3afe949 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #24 0x00007fe9d20b49af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007fe9d20a92a0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007fe9d2b4ef4e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x00007fe9d207d618 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x00007fe9d20805b1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x00007fe9d20d5ae3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x00007fe9cfaf2729 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x00007fe9cfaf29b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x00007fe9cfaf2a4c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x00007fe9d20d51c6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x00007fe9d207c09b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x00007fe9d2084206 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x0000562311ab5d55 in ?? () #37 0x00007fe9d19da20a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #38 0x00007fe9d19da2bc in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #39 0x0000562311ab612a in ?? () [Inferior 1 (process 2816942) detached] Reported using DrKonqi
Hi, have you encountered this bug again on newer setup?
(In reply to Akseli Lahtinen from comment #1) > Hi, have you encountered this bug again on newer setup? Hi, No, so far no errors! All is good.
Thanks, setting this fixed :)