Created attachment 191677 [details] Screenshot of the component after it appears (~1 minute after clicking the attach button). *** 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 KDE filechooser (or whatever the file selection component is) freezes / takes a minute to start when the last location was a network drive that is no longer present. STEPS TO REPRODUCE 1. Mount a network drive. 2. Click any "Browse" or "Attach" button in Firefox under KDE. 3. Navigate to the network drive and attach a file. 4. Unmount that network drive. 5. Click any "Browse" or "Attach" button in Firefox under KDE. OBSERVED RESULT KDE filechooser appears only after a very large delay, as it attempts to navigate to the unmounted drive. It then also freezes for a few seconds once one attempts to select a valid location, e.g. Home. EXPECTED RESULT KDE filechooser should appear instantly, perhaps with the file selector part grayed out; the quick-select panel should remain responsive. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.6.3 KDE Frameworks Version: 6.24.0 Qt Version: 6.11.0
I wonder what causes the delay. The dialog may try to ask kio-fuse what the original URL for that share was, but that doesn't need any request. If the location was mounted previously but no longer exists, there should be an immediate error. Only idea I currently have is that the location is initially mounted during first use, then the server becomes unreachable for whatever reason (like a network change) and every request runs into a time out, but that does not match the unmounting. Does the parent folder exist and exhibit the same issue? Do you have the systemd user journal for the time of the delay? I currently don't have any smb: server available to attempt reproduction of this issue.
(In reply to Fabian Vogt from comment #1) > I wonder what causes the delay. The dialog may try to ask kio-fuse what the > original URL for that share was, but that doesn't need any request. If the > location was mounted previously but no longer exists, there should be an > immediate error. Only idea I currently have is that the location is > initially mounted during first use, then the server becomes unreachable for > whatever reason (like a network change) and every request runs into a time > out, but that does not match the unmounting. > > Does the parent folder exist and exhibit the same issue? > > Do you have the systemd user journal for the time of the delay? > > I currently don't have any smb: server available to attempt reproduction of > this issue. Hi Fabian, Thanks for checking, I tried it again at work today (where I have access to the SMB drive). My "how to reproduce" instructions are not correct; it doesn't happen when the drive is correctly unmounted! It does happen when I switch the vpn off (by ctrl+c; openconnect) or when I eject the laptop from the dock (which switches from ethernet to wifi connection and which makes the shared drive unavailable). So it must be some kind of timeout.