SUMMARY System D automounted NFS Shares that are offline cause Dolphin not to load. This is similar to another bug reported previously for plasma, but that one was marked resolved and did not mention Dolphin. I'm hoping a similar resolution will work here. STEPS TO REPRODUCE 1. Have fstab like this for nfs share pc:/nfs-share /mnt/pc/nfs-share nfs auto,user,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=5 0 0 2. Attempt to launch dolphin via konsole or menu OBSERVED RESULT The application does not load, it is not responding EXPECTED RESULT The application should ideally load in spite of the nfs mount not being available (in this case due to a power outage). SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.1-arch1-1 64-bit (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Graphics Platform: X11
I have the same issue. It looks like dolphin tries to mount the unavailable network share each time it loads a new directory. The slowdown is probably caused by dolphin waiting for the automount actually starting the loading of the directory. A possible solution might be to handle dolphin aoutomounts on a separate process so the directory browsing would not be interrupted by a failing mount. As a temporary fix I comment out the line in /etc/fstab containing the mount options for the offending share.
This has been happening to me for years. There have been a few previous bug reports but they usually get buried. The shares don't have to be offline for dolphin to freeze, just busy. Dolphin can actually make itself freeze if you copy a file to the share and it saturates the connection. Dolphin will stall until the transfer to the share is finished. If the share goes down, dolphin will stay frozen forever.
I don't understand why this is getting so little attention - wouldn't this impacting everyone ? On my distro (Manjaro, unstable, up to date) with Dolphin 23.08.2 I have exactly the described behavior: slow loading of large folders - which still occurs despite having been addressed in bug #442106, and completely frozen and unresponsive application when the nfs shares are not available (NAS not started or not reachable). Also, copying a large file to/from the nfs share will freeze the whole Dolphin interface. Using a GTK based application on the same conditions results in normal behavior / delays. There was a poor decision somewhere in the KDE's framework library and/or Dolphin that renders it dreadful when the conditions are met. Is there a way we can help with the investigation ?
(In reply to battyanyi.dani from comment #1) > I have the same issue. It looks like dolphin tries to mount the unavailable > network share each time it loads a new directory. As a Krusader fan I can say that the issue is not limited to just Dolphin, and I don't think the issue is with mounting as an already mounted share becoming unresponsive is also causing such issues. It's likely to be a matter of either both Dolphin and Krusader trying to get info on mounts in the background for something like disk usage measurement, or KIO is serving too much information somewhere, poking all mounts even when not desired. (In reply to SoftExpert from comment #3) > I don't understand why this is getting so little attention - wouldn't this > impacting everyone ? Unlikely to be common at least on the local network. My rather weak server sharing a slow HDD is not affected in normal circumstances, it only gets slow when I'm well aware I'm abusing it with I/O. Other than that I use the SFTP KIO slave for high latency targets which is surely slow, but by not being a mount it doesn't exhibit this issue. The issue possibly got better over time with the addition of some timeout, or I just happened to be "lucky" because the share wasn't in use so the symptoms weren't severe last time I've seen it. It would be interesting to confirm though whether my Krusader usage mattered there and Dolphin still freezes. Although I haven't used Dolphin last time, confirming the issue because it's a known problem, and I happened to "enjoy" waiting for timeouts quite recently with Krusader as I was messing with the network making the mounted NFS share's server unavailable. Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-15-generic (64-bit)