Application: dolphin (24.02.1) Qt Version: 6.7.0 Frameworks Version: 6.0.0 Operating System: Linux 6.8.2-arch1-Adashima-T2-1-t2 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.3 [CoredumpBackend] -- Information about the crash: To reproduce the crash, 1. drag any item to any text section of the path breadcrumb 2. dolphin crashes The crash occurred even after a fresh restart. I am not aware of any non-default settings, apart from using a theme. The crash can be reproduced every time. -- Backtrace (Reduced): #5 QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::get (this=0x8, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/tools/qscopedpointer.h:110 [...] #8 QObject::deleteLater (this=0x0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:2456 #9 0x000071d3d3903dfe in KDEPrivate::KUrlNavigatorButton::dragMoveEvent (this=0x6309d8f5d230, event=<optimized out>) at /usr/src/debug/kio/kio-6.0.0/src/filewidgets/kurlnavigatorbutton.cpp:323 #10 0x000071d3d23470d3 in QWidget::event (this=0x6309d8f5d230, event=0x7fffbe8f8ac0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:9237 #11 0x000071d3d22fbfcb in QApplicationPrivate::notify_helper (this=this@entry=0x6309d8c28030, receiver=0x6309d8f5d230, e=e@entry=0x7fffbe8f8ac0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287 Reported using DrKonqi
Created attachment 168297 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
I couldn't reproduce the bug though. Could you provide more precise scenario or a video capture ? May have be taken of by https://invent.kde.org/frameworks/kio/-/commit/341a75c7e42ea8bcea07d0a0c0044a5a4f342e07
Created attachment 168300 [details] Screencast of the reproduction of the bug I don't really know how to describe it more precisely so I've attached a screencast to demonstrate the behavior. Will test the patch later.
(In reply to Sophie Cheung from comment #3) > Created attachment 168300 [details] > Screencast of the reproduction of the bug > > I don't really know how to describe it more precisely so I've attached a > screencast to demonstrate the behavior. Will test the patch later. I don't reproduce it. Do you reproduce it with breeze ? I think I fixed already anyway.
*** Bug 485361 has been marked as a duplicate of this bug. ***
*** Bug 485413 has been marked as a duplicate of this bug. ***
*** Bug 485428 has been marked as a duplicate of this bug. ***
*** Bug 485465 has been marked as a duplicate of this bug. ***
*** Bug 485714 has been marked as a duplicate of this bug. ***
*** Bug 485757 has been marked as a duplicate of this bug. ***
*** Bug 485977 has been marked as a duplicate of this bug. ***
*** Bug 486054 has been marked as a duplicate of this bug. ***
*** Bug 486146 has been marked as a duplicate of this bug. ***
Only rolling release distro will get confronted with this. Those distro updated Qt to 6.7 before devs even started using it and Qt 6.7 introduced some very low-level behavior changes causing crashes (deleteLater() now crash when called with a nullptr object, most likely because of https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/kernel/qobject.cpp?h=v6.7.0&id=d50746ef3aec72d339f639395a2291009f186680)
*** Bug 486479 has been marked as a duplicate of this bug. ***
(In reply to Méven Car from comment #14) > Only rolling release distro will get confronted with this. > Those distro updated Qt to 6.7 before devs even started using it and Qt 6.7 > introduced some very low-level behavior changes causing crashes > (deleteLater() now crash when called with a nullptr object, most likely > because of > https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/kernel/qobject. > cpp?h=v6.7.0&id=d50746ef3aec72d339f639395a2291009f186680) Yes, before scrolling through the archlinux update I looked at the about to be updated package, which includes qt, after updating qt, Then this bug appeared（Translated）
(In reply to Méven Car from comment #14) > Only rolling release distro will get confronted with this. > Those distro updated Qt to 6.7 before devs even started using it and Qt 6.7 > introduced some very low-level behavior changes causing crashes > (deleteLater() now crash when called with a nullptr object, most likely > because of > https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/kernel/qobject. > cpp?h=v6.7.0&id=d50746ef3aec72d339f639395a2291009f186680) Having same behavior on KDE Neon I suppose in Neon QT must be used by devs Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 15.3 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Dell Inc. Product Name: XPS 15 9570
*** Bug 471279 has been marked as a duplicate of this bug. ***
*** Bug 485786 has been marked as a duplicate of this bug. ***
*** Bug 486579 has been marked as a duplicate of this bug. ***
*** Bug 486454 has been marked as a duplicate of this bug. ***
*** Bug 486065 has been marked as a duplicate of this bug. ***
*** Bug 486702 has been marked as a duplicate of this bug. ***
*** Bug 486758 has been marked as a duplicate of this bug. ***
*** Bug 486824 has been marked as a duplicate of this bug. ***
*** Bug 486843 has been marked as a duplicate of this bug. ***
*** Bug 486868 has been marked as a duplicate of this bug. ***
*** Bug 486859 has been marked as a duplicate of this bug. ***
*** Bug 486879 has been marked as a duplicate of this bug. ***
*** Bug 486944 has been marked as a duplicate of this bug. ***
*** Bug 486950 has been marked as a duplicate of this bug. ***
This bug is currently marked as "RESOLVED FIXED". I'm in KDE neon and the bug is still present (it often annoys me). Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland Can someone confirm that it has been fixed and that I just have to wait for the update to come ?
I'm on Fedora 40 an according to the "About This System" tool, I have: Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland This bug is not currently happening so, looks fine.
(In reply to David Tonhofer from comment #33) > I'm on Fedora 40 an according to the "About This System" tool, I have: > > Operating System: Fedora Linux 40 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.2.0 > Qt Version: 6.7.0 > Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) > Graphics Platform: Wayland > > This bug is not currently happening so, looks fine. Ok. I am not on the latest KDE Frameworks version. I forgot that I had slow down a bit updates in system settings (it's good to be able to not receive updates at each days).
I can confirm that it is now fixed for me.
*** Bug 487463 has been marked as a duplicate of this bug. ***
*** Bug 487269 has been marked as a duplicate of this bug. ***