Created attachment 187609 [details] coredumpctl output for dolphin being force closed while unresponsive SUMMARY When I launch Dolphin, or anything that uses dolphin, I get a significant hang where I am unable to interact with the window for several seconds before everything recovers and performs like normal. I am not attempting to open any network file shares and the issue persists even if I unmount every drive except for my required drives like /root and /home. I can even replicate the issue on a fresh user account. The issue also extends to stuff like the file picker. STEPS TO REPRODUCE 1. launch dolphin 2. dolphin hangs for about 10 seconds 3. dolphin recovers and resumes operating as normal OBSERVED RESULT Dolphin has an extended period of unresponsiveness after launching EXPECTED RESULT Dolphin is usable extremely soon after lunch with no significant hang SOFTWARE/OS VERSIONS Operating System: Fedora Linux 43 KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.21.0 Qt Version: 6.10.1 Kernel Version: 6.17.11-300.fc43.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 32 GiB of RAM (31.3 GiB usable) Graphics Processor 1: AMD Radeon RX 7800 XT Graphics Processor 2: NVIDIA GeForce RTX 3070 Ti ADDITIONAL INFORMATION The core dump I have attached has been triggered by trying to interact with dolphin until I am prompted to terminate the application, at which point it core dumps and I can get some debug info out of it. If I don't do that, I get no debug info and things recover like nothing even happened.
Created attachment 187610 [details] valgrind output from running dolphin
bug 474100 looks similars and has GDB trace
i've been experiencing the same thing on arch/cachy os! in both the native version and the nix one (not on the flatpak version tho) one thing i noticed is that, at least to me, it only happens when dolphin sees a folder. that is, if you launch it in a folder with no folders inside, it will work absolutely just fine, then if you go to another folder with other folders inside, or maybe even create a folder inside the one without folders, it will get the 10s of unresponsiveness until it gets back to normal and then dolphin seems completely normal. and it's not exclusive to dolphin the app itself, file pickers are also seem to be affected!
i tried downgrading it to even like a 2024 version and the bug persisted so i'm assuming it's probably something around it instead of dolphin itself, but i really don't know much about this so that's all i can say
(In reply to Ayla from comment #4) > i tried downgrading it to even like a 2024 version and the bug persisted so > i'm assuming it's probably something around it instead of dolphin itself, > but i really don't know much about this so that's all i can say I think it might be related to Kioworker and ffmpeg since I was seeing crashes in the flatpak version related to that while it was trying to generate thumbnails but that stopped when I deleted all the videos in my home directory and dolphin is still non-responsive when not using the flatpak.
ooh i found something. it seems to be internet related because disabling my wifi makes it load instantly!
seems like this is what is happening! removing my samba config from the folder makes it stop freezing too! https://discussion.fedoraproject.org/t/dolphin-freeze-for-8-seconds-when-opening-fedora-43-kde-solved/178398
(In reply to Ayla from comment #6) > ooh i found something. it seems to be internet related because disabling my > wifi makes it load instantly! I can replicate this behavior. Which is wild because I'm not loading any network drives.
(In reply to Ayla from comment #7) > seems like this is what is happening! removing my samba config from the > folder makes it stop freezing too! > https://discussion.fedoraproject.org/t/dolphin-freeze-for-8-seconds-when- > opening-fedora-43-kde-solved/178398 and I can confirm that does indeed solve the freezing issue. What is wild is that I'm using a smb.conf that shipped with the samba package on fedora...
for the record i will put here a transcript of the fedora forums post https://discussion.fedoraproject.org/t/dolphin-freeze-for-8-seconds-when-opening-fedora-43-kde-solved/178398 Dolphin freeze for 8 seconds when opening - Fedora 43 KDE [SOLVED] Ask Fedora Dec 2025 27d ago post by hfine on Dec 24, 2025 Harry Fine hfine 27d I’m writing this because I’ve spent about 5 hours trying to resolve this without luck until finally, I hit gold. This is a new install, a week old, using the newest KDE version with all updates installed. BTW, I love the Fedora sweet-spot of stability along with recent packages. I did a lot of straces, went down many rabbit holes, but couldn’t stop dolphin hanging for 8 seconds before being responsive in any way (even closing the window). I have fuser mounts running, Google Drive and sshfs to other machines including my Synology NAS using systemd so I was chasing down those. Edited the service files. No change. Changed every setting in Dolphin that might have it looking at places or remotes. No change. Did all sorts of diagnostics with kio-fuse, kio-worker, dbus monitoring, xdg-document-portal stale fuse mounts, clearing caches, restricting file searches, checking suspect services, tracking down file descriptors and sockets, disabling the network, session manager communication, virtualbox shared folder, /etc/hosts file, bad user-dirs.dirs directory, font cache corruption Finally I ran Dolphin with QT_LOGGING_RULES="*.debug=true", I saw a specific error message: QT_LOGGING_RULES="*.debug=true" dolphin 2>&1 | grep -i "kio" > kf.kio.core: We got some errors while running testparm "Weak crypto is allowed..." This proved that KIO (KDE’s input/output architecture) was calling testparm to check security settings. Because the Samba config was “ambiguous” or “legacy,” the check triggered a GnuTLS security timeout. After some Googling, it seems Fedora has moved to stricter crypto policies than on my previous installs. The standard min protocol = SMB2 is now considered too broad/weak by the system’s libraries. The fix was to explicitly define SMB2_10 and forcing ntlmv2-only or disabled satisfies the security check instantly, allowing the KIO worker to finish and the Dolphin UI to populate. client min protocol = SMB2_10 server min protocol = SMB2_10 client ipc min protocol = SMB2_10 ntlm auth = ntlmv2-only This was likely my error moving my smb.conf file froma previous installation of MX or Mint. I hope someone finds this useful.