Version: unspecified (using KDE 4.6.2) OS: Linux With a samba share mounted via /etc/fstab an entry is automatically created in the Places panel. If Dolphin is started and this share is not available on the current network Dolphin becomes unusable to the point that it has to be forcefully terminated. Reproducible: Always Expected Results: Unavailable shares should be ignored. OS: Linux (x86_64) release 2.6.38-8-generic Compiler: cc
*** Bug 337425 has been marked as a duplicate of this bug. ***
*** Bug 288158 has been marked as a duplicate of this bug. ***
*** Bug 354750 has been marked as a duplicate of this bug. ***
*** Bug 274673 has been marked as a duplicate of this bug. ***
*** Bug 292580 has been marked as a duplicate of this bug. ***
*** Bug 335498 has been marked as a duplicate of this bug. ***
*** Bug 344153 has been marked as a duplicate of this bug. ***
*** Bug 354475 has been marked as a duplicate of this bug. ***
*** Bug 356962 has been marked as a duplicate of this bug. ***
*** Bug 328772 has been marked as a duplicate of this bug. ***
*** Bug 283366 has been marked as a duplicate of this bug. ***
Per dupes, this applies to multiple distros, not just *buntu. And it's not just about Samba, but NFS as well.
*** Bug 320560 has been marked as a duplicate of this bug. ***
Clarify "not available", please!
When they're on a part of a network that you're not on. For example: you have a samba share mounted via an entry in /etc/fstab for your home music, video, or backup server and you make a Places panel entry for it. Then you take your laptop and go to a coffee shop and connect to their wifi network. The samba mount is no longer available.
> Clarify "not available", please! That's the right question to ask, because blindly duplicating things to this bug does not really help. The problem is with places which are still mounted through non-KIO mechanisms, although their backing server is not accessible anymore (network down, server stopped etc.). If you have no coffee shop nearby, follow those steps to reproduce: - Configure and start samba server on localhost, share folder from Dolphin. - "mount -t cifs" this folder to /mnt, Dolphin should automatically add an entry to the "Remote" section. - Navigate to the new entry, "Add to places". - Stop samba server without umounting first. - Observe how clicking on both entries in the places panel results in a hang, which only after a long timeout is resolved with "Could not enter folder /mnt". - Another way to trigger is via the places panel in the file dialog or in Gwenview, where hovering over an entry (so the free space is calculated) is enough to cause a hang. Not affected are places which are accessed via a KIO slave, e.g. fish:/ or smb:/. Also note the emphasis on "clicking on or hovering over the entry". If e.g. Gwenview hangs on startup without clicking on anything, that's obviously not caused by the places panel, but by its "Recent Folders" panel. In addition, some duplicated bugs were about accessing local folders without clicking on remote ones. I believe that has been fixed some time ago by making the places panel query free space information only on hover, but not on every relayout or opening of the file dialog. Another thing to watch out for is when a "delay" is reported vs. a "hang". The first is caused by autofs taking some time until the mount is eventually available, the latter is caused by the complete unavailability of the mount. Note as well that a non-autofs place which is not yet mounted will not cause a hang, the hang only occurs when the place is mounted (i.e. it has been available before) but the server times out at a later point in time. Yet another related issue is Bug 288158 (which has also been duplicated to this bug), where accessing a faulty CD causes freezes. Same thing for Bug 337425, which is about "slow" (but still available) mounts. All that makes me wonder whether this bug should not be about "unavailable mounts", but about mounts which are timing out. I doubt there is much KDE can do here in terms of preventing this timeout in the mount itself, because even an "ls /mnt" will show the same behaviour. What could be done is: - On the system level: Find a way to auto-umount mountpoints which are gone (would only help for a subset of the duplicates), or drastically reduce the timeout (would help in every case). - In the places panel and in each application separately: Mitigate the effects on the user experience, i.e. instead of hanging on startup or when clicking on things, run the checks in the background so the UI remains interactive. --- @Nate: Please go through all bugs you duplicated to this one and make sure they are really about the same issue. Otherwise unduplicate, close if fixed or duplicate to the proper bug.
A bug marked as a duplicate of this affects gwenview when KDEConnect is active. gwenview hangs (GUI unresponsive and undrawn) for 25 s. This is not some mount not available; the "Device" in dolphin works fine, with no delay. If the phone paired through KDEConnect is unpaired there is no problem.
IIUC there are two different Places panels, one from KIO (which is used in e.g. the open file dialog that you can invoke from kwrite or kate), and one from Dolphin, do both have the issue?
I would reference also the bug #454722 - Dolphin becomes frozen if nfs shares declared in fstab are not available - previously the mount point was just showing empty. Currently reproduced with Dolphin 23.08.2.