Application: dolphin (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.7.12+bpo-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Only happened once, but I had two tabs open. one was local, one was a sshfs "host not found" error. I was in the url bar of the latter, and I pressed Ctrl-T, Dolphin crashed, The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #6 0x00007fe39fa855c8 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #7 0x00007fe39dce8f8f in QtPrivate::QSlotObjectBase::call (a=0x7ffc524269c0, r=0x7fe39fb065c0, this=0x55f57d5b4e70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate<false> (sender=0x55f57d606e10, signal_index=6, argv=0x7ffc524269c0) at kernel/qobject.cpp:3923 #9 0x00007fe39dce222f in QMetaObject::activate (sender=sender@entry=0x55f57d606e10, m=m@entry=0x7fe39f1fb180 <KJob::staticMetaObject>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc524269c0) at kernel/qobject.cpp:3983 #10 0x00007fe39f19f775 in KJob::result (this=this@entry=0x55f57d606e10, _t1=<optimized out>, _t1@entry=0x55f57d606e10, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #11 0x00007fe39f1a0c5b in KJob::finishJob (this=0x55f57d606e10, emitResult=<optimized out>) at ./src/lib/jobs/kjob.cpp:98 #12 0x00007fe39dce8f8f in QtPrivate::QSlotObjectBase::call (a=0x7ffc52426a80, r=0x55f57d606e10, this=0x55f57d9f0390) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate<false> (sender=0x55f57d8358f0, signal_index=7, argv=0x7ffc52426a80) at kernel/qobject.cpp:3923 #14 0x00007fe39fa12713 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x00007fe39fa10d56 in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #16 0x00007fe39fa15ac9 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #17 0x00007fe39dce8f8f in QtPrivate::QSlotObjectBase::call (a=0x7ffc52426cd0, r=0x55f57d8358f0, this=0x55f57d606690) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate<false> (sender=0x55f57da41f70, signal_index=3, argv=0x7ffc52426cd0) at kernel/qobject.cpp:3923 #19 0x00007fe39dcdd730 in QObject::event (this=0x55f57da41f70, e=0x55f57d606d20) at kernel/qobject.cpp:1347 #20 0x00007fe39e962fae in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55f57da41f70, e=0x55f57d606d20) at kernel/qapplication.cpp:3640 #21 0x00007fe39dcb1738 in QCoreApplication::notifyInternal2 (receiver=0x55f57da41f70, event=0x55f57d606d20) at kernel/qcoreapplication.cpp:1064 #22 0x00007fe39dcb18fe in QCoreApplication::sendEvent (receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1462 #23 0x00007fe39dcb46c1 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55f57c433f50) at kernel/qcoreapplication.cpp:1821 #24 0x00007fe39dcb4b48 in QCoreApplication::sendPostedEvents (receiver=<optimized out>, event_type=<optimized out>) at kernel/qcoreapplication.cpp:1680 #25 0x00007fe39dd0a193 in postEventSourceDispatch (s=0x55f57c595e10) at kernel/qeventdispatcher_glib.cpp:277 #26 0x00007fe39b91e7a9 in g_main_dispatch (context=0x7fe390005010) at ../../../glib/gmain.c:3454 #27 g_main_context_dispatch (context=context@entry=0x7fe390005010) at ../../../glib/gmain.c:4172 #28 0x00007fe39b91ea38 in g_main_context_iterate (context=context@entry=0x7fe390005010, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4248 #29 0x00007fe39b91eacc in g_main_context_iteration (context=0x7fe390005010, may_block=1) at ../../../glib/gmain.c:4313 #30 0x00007fe39dd09876 in QEventDispatcherGlib::processEvents (this=0x55f57c59d3b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #31 0x00007fe39dcb01bb in QEventLoop::exec (this=this@entry=0x7ffc524270c0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #32 0x00007fe39dcb8316 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #33 0x000055f57bffb142 in ?? () #34 0x00007fe39d84624a in __libc_start_call_main (main=main@entry=0x55f57bff9ed0, argc=argc@entry=1, argv=argv@entry=0x7ffc52427378) at ../sysdeps/nptl/libc_start_call_main.h:58 #35 0x00007fe39d846305 in __libc_start_main_impl (main=0x55f57bff9ed0, argc=1, argv=0x7ffc52427378, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc52427368) at ../csu/libc-start.c:360 #36 0x000055f57bffb591 in ?? () [Inferior 1 (process 72383) detached] Reported using DrKonqi
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, (Plasma 6 session, where the handling of mounting sshfs mounts is different) and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #6 0x00007fe39fa855c8 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
This bug looks related to bug 490130
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Annoyingly I can't seem to reproduce this since I installed the debug symbols. I have caused it to crash multiple times before, but it's a specific network error that seems to cause this.
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
I was so excited I reproduced this this morning, until the bug report utility crashed trying to upload the new stack trace. Is there some place I can look for the stack trace?
Thanks for being willing to add your backtrace. Take a look at this to see how to get it from disk: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?
Unfortunately, it looks like that list caught the drkonqi crash, but not the dolphin crash. I will hope it crashes again soon
.