Created attachment 185482 [details] Second Dolphin Core Dump *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Supposedly, the issue reported in bug 451050 was marked as `RESOLVED FIXED`, however, it seems like it's happening again. This issue was first reported Downstream (nixpkgs), but one of the maintainers recommended me to report it Upstream. As such, I will link the Downstream issue, and this bug report within the issue. Seemingly, a similar (if not equal) bug is occurring, where if you try to open a Samba share with Dolphin, Dolphin crashes. STEPS TO REPRODUCE 1. Open Dolphin 2. Attempt to open a Samba Shared Folder OBSERVED RESULT Dolphin crashes, throwing a `SIGSEGV` to the terminal with the following error message `kf.kio.core: Internal error: itemsInUse did not contain QUrl("smb://<USER>@<IP>/")`. EXPECTED RESULT Dolphin should be able to open the Samba Shared Folder. LOGS The core dump after the crash can be seen within the Downstream issue, but I've also attached the core dump of the second time I tried to open a folder, after updating and restarting my system. SOFTWARE/OS VERSIONS Operating System: NixOS 25.11 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.9 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 16 GiB of RAM (15.0 GiB usable) Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION The Downstream issue can be found in https://github.com/NixOS/nixpkgs/issues/448208
As stated Downstream, this issue fixed itself after some time, seemingly for no reason. I'll close this report, it can be reopened if someone else reports it.
Found out that Dolphin added the user automatically, hence it working. If the user's not specified, the crash still occurs.
Please attach a backtrace of the crash
(In reply to David Redondo from comment #3) > Please attach a backtrace of the crash I am not sure if I can. I've read the HOWTO about creating crash reports (Which I forgot to remove from the report, my bad), but I am not sure if NixOS has debug enabled packages. I tried asking about it on the Downstream issue, but it seems like the response was no? Not sure honestly, so here's the response: https://github.com/NixOS/nixpkgs/issues/448208#issuecomment-3366238478
🐛🧹 ⚠️ 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!
Not sure if this has the necessary debug information, but Dr. Konqi gave the following report: ``` Starting debugger /nix/store/qgrqwj2qidrywwfih67hwx2sf34h0y7m-gdb-host-cpu-only-16.3/bin/gdb --init-eval-command=set auto-solib-add off --nw --nx --batch --command=/tmp/drkonqi.IquBQN --command=/tmp/drkonqi.oAxONl --core=/tmp/drkonqi-core.QAoiFY/core /nix/store/95mcb1zkxrmmhxhq1r8ggsziy5wqzi7y-dolphin-25.08.2/bin/.dolphin-wrapped warning: Can't open file /memfd:sljit (deleted) during file-backed mapping note processing warning: Can't open file /memfd:wayland-shm (deleted) during file-backed mapping note processing [New LWP 12173] [New LWP 12176] [New LWP 12178] [New LWP 12177] [New LWP 12181] [New LWP 12183] [New LWP 12184] [New LWP 12180] [New LWP 12195] [New LWP 12194] [New LWP 12193] [New LWP 12216] [New LWP 12196] [New LWP 12192] [New LWP 12204] [New LWP 12206] [New LWP 12179] [New LWP 12203] [New LWP 12208] [New LWP 12182] [New LWP 12209] [New LWP 12217] [New LWP 12218] [New LWP 12175] [Thread debugging using libthread_db enabled] Using host libthread_db library "/nix/store/daamdpmaz2vjvna55ccrc30qw3qb8h6d-glibc-2.40-66/lib/libthread_db.so.1". Core was generated by `/run/current-system/sw/bin/dolphin'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f911209caac in __pthread_kill_implementation () from /nix/store/daamdpmaz2vjvna55ccrc30qw3qb8h6d-glibc-2.40-66/lib/libc.so.6 [Current thread is 1 (Thread 0x7f910b41dd00 (LWP 12173))] Traceback (most recent call last): File "/nix/store/7chsmm0mxgas09c7ynn5776ry3gszxkq-drkonqi-6.5.0/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 608, in print_preamble print_preamble_internal() ~~~~~~~~~~~~~~~~~~~~~~~^^ File "/nix/store/7chsmm0mxgas09c7ynn5776ry3gszxkq-drkonqi-6.5.0/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 582, in print_preamble_internal resolve_modules() ~~~~~~~~~~~~~~~^^ File "/nix/store/7chsmm0mxgas09c7ynn5776ry3gszxkq-drkonqi-6.5.0/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 577, in resolve_modules image = CoreImage(line) File "/nix/store/7chsmm0mxgas09c7ynn5776ry3gszxkq-drkonqi-6.5.0/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 545, in __init__ raise NoBuildIdException(f'No build id found in core image: {eu_unstrip_line}') NoBuildIdException: No build id found in core image: 0x7f90b0008000+0xd010 - /nix/store/0vdhbsw15wcllh9q0jvhyzgn8asmavfi-libwebp-1.6.0/lib/libwebpmux.so.3 - libwebpmux.so.3 No build id found in core image: 0x7f90b0008000+0xd010 - /nix/store/0vdhbsw15wcllh9q0jvhyzgn8asmavfi-libwebp-1.6.0/lib/libwebpmux.so.3 - libwebpmux.so.3 Sentry is attempting to send 2 pending events Waiting up to 30 seconds Press Ctrl-C to quit Debugging ended with exit code '1' and exit status 'NormalExit' ```
Also, as reported within the Downstream issue, this has the same situation that bug 451050 where specifying a folder from the share avoids this crash.