When Dolphin has a link to a currently inaccessible share in the sidebar it takes a *very* long time for it to timeout. Reproducible: Always Steps to Reproduce: 1. Use automount to map an NFSv4 server share at /net/server 2. Place a shortcut to /net/server in the Dolphin sidebar 3. Open Dolphin when the network is disconnected (like say on a *laptop* that's remote and doesn't happen to have access to that host at the moment) 1. 2. 3. Actual Results: Watch the completely empty Dolphin app frame do nothing for ten minutes Expected Results: An error dialog displayed immediately Why even check the validity of the share until it's sidebar link is actually clicked on? I think it's better to wait until the sidebar link is actually clicked on and then throw an inaccessible error dialog instead of sitting there at app startup, for much too long, trying to validate the links. For laptop users that travel this is a painful issue.
Thanks for the bug report! Unfortunately, I don't have any NFS shares to test with. Do you know if this problem is new in KDE 4.9? In that case, it's been caused by the Places Panel rewrite, and we could maybe check by comparing with the code in KFilePlaces* from kdelibs what goes wrong.
Resetting assignee to default as per bug #305719
Hi Frank, I don't know if it's an issue with 4.9 or not yet, I'm still on 4.8.5. One more thing that I discovered today is that maunally mounted NFS shares that are automatically included in the panel create the same issue - if the server goes away Dolphin becomes completely unresponsive and goes off into never-never land (for 10 minutes and counting now). This occurs even if the current directory in Dolphin is not open to the mountpoint.
I've confirmed that this still occurs on 4.9 but it seems to be less of an issue and Dolphin seems to recover faster.
*** This bug has been marked as a duplicate of bug 302295 ***