Bug 511434

Summary:	Dolphin changes location after sleep/hibernate, saying current (NFS) directory is no longer accessible
Product:	[Applications] dolphin	Reporter:	S. Bryant <steve>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	dolphin-bugs-null
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=500413
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description S. Bryant 2025-10-31 16:36:57 UTC

SUMMARY
I mount some directories from my NAS using NFS.  My desktop is typically hibernated when not in use.

STEPS TO REPRODUCE
1. Navigate in Dolphin to a directory on an NFS mount
2. Hibernate the computer
3. Wait
4. Resume the computer

OBSERVED RESULT
Dolphin says the directory is no longer accessible and changes location (typically to $HOME).

EXPECTED RESULT
Dolphin allows the computer to re-establish NFS mounts on resume, and only counts the directory as no longer accessible after a short timeout.  A few hundred ms (<1s) is likely enough; if NFS takes "too long" to become available, it can legitimately be deemed no longer accessible.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: openSUSE Tumbleweed-Slowroll 20251002
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
Resuming immediately does not exhibit this behaviour.  I assume an NFS timeout is involved.

It seems likely that this could affect other types of networked filesystem mounted by the kernel, but I have not tested this.