https://bugs.kde.org/show_bug.cgi?id=423187
--- Comment #24 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- (In reply to Jens from comment #23) If what you're seeing is indeed an example of https://discuss.kde.org/t/34436?u=rokejulianlockhart, and if you continue to reproducibly wait minutes, try launching Dolphin, ascertaining what its PID is (you can enable the relevant column in System Monitor's Processes page), attaching `strace -Tr -p $id`, and ASAP attempting to access that unresponsive external storage. During reproduction, check your terminal (this works best if you have the terminal and Dolphin vertically adjacent, both always visible irrespective of which window is focussed), and you should see not very much activity, or a lot of repetition. Wait until Dolphin eventually becomes responsive, then quickly kill Dolphin, and send over the syscall that shows via its timestamp that it took over a minute to elapse. By the way, if you're familiar with KDAB's Hotspot, `perf` might also record something useful. 🤷 I would do this myself, but reproduction is less consistent for me, when accessing a FISH URI for a shut-down VM. -- You are receiving this mail because: You are watching all bug changes.
