Application: dolphin (25.04.0) ApplicationNotResponding [ANR]: false Qt Version: 6.9.0 Frameworks Version: 6.13.0 Operating System: Linux 6.14.3-zen1-1-zen x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.3.4 [CoredumpBackend] -- Information about the crash: I accessed an SMB share on my network, typed in my credentials, and crash. Typing in the incorrect credentials does not crash. It seems to fail to list the items in the share. This has happened with both of my network shares, coming from different systems with different OSes (Synology NAS, Windows 11) and did not happen previously when I was on (I believe) 24.12.3-1 - I am now on 205.04.0-1. Additionally, stdout shows this on crash - the exact value in KDirListener changes each crash, but every other detail is identical. ``` kf.kio.core: Internal error: itemsInUse did not contain QUrl("smb://tap@taps-vr-pc/") kf.kio.core: Fatal Error: HUH? Lister KDirLister(0x5e20d7d0bea0) is supposed to be listing, but has no job! KCrash: Application 'dolphin' crashing... crashRecursionCounter = 2 Aborted (core dumped) ``` The crash can be reproduced every time. -- Backtrace (Reduced): #5 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x00007c6a684a56d3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89 #7 0x00007c6a6844bba0 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007c6a68433582 in __GI_abort () at abort.c:73 #9 0x00007c6a6ae9a30f in KCoreDirListerCache::printDebug (this=this@entry=0x5805e7e5c810) at /usr/src/debug/kio/kio-6.13.0/src/core/kcoredirlister.cpp:2093 Reported using DrKonqi
Created attachment 180523 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
*** This bug has been marked as a duplicate of bug 503165 ***
This is actually bug 451050 *** This bug has been marked as a duplicate of bug 451050 ***
This bug has not been resolved, and the duplicates are pointing to one another in a loop.
The backtrace in this bug report is the same trace as bug 505396 that you also reopened Both of these bugs have the same backtrace as 451050, which is the parent report for this crash. Having multiple open reports for the same backtrace doesn't help us fix the crash. In 451050 it was noted that this is fixed in Frameworks 6.16 If you still see this crash with Frameworks 6.16, please leave this report closed and make a note in bug 451050. *** This bug has been marked as a duplicate of bug 451050 ***