https://bugs.documentfoundation.org/show_bug.cgi?id=152859
--- Comment #11 from Alex Thurgood <[email protected]> --- My guess is this. Initialization of the LO Finder dialog appears to be a fork() in the main LO process. Whenever a network resource is unavailable, that fork appears to fail to return to the main LO process, causing a hang instead of gracefully handling the situation by presenting a helpful message to the user such as "Network resource unavailable, please mount the network resource and try again", closing the Finder dialog and returning to the main LO UI which should regain the focus. The additional question to be solved would be how to manage the time it takes Finder to realize that the network resource is unavailable. As anyone who works with macOS in a networked environment knows, accessing remote files can variously take between a few seconds, and several minutes, depending on the remote file system being accessed. I doubt that the LO process can have any influence on those timeouts. I imagine that one way around this would be to use the native LO dialogs and define a shorter timeout there, but then the user would lose the convenience of the Finder dialog and obviously the UI experience. -- You are receiving this mail because: You are the assignee for the bug.
