Version: 1.7 (using KDE 4.7.2) OS: Linux I mount a network path through cifs using /etc/fstab. After the server is going down the network path will not be available anymore but is still mounted and has to be unmounted. That's ok for me and I can unmount manually that server suddenly available anymore. But the big problem is, that dolphin is still trying to access the network path although it hasn't opened that path. Dolphin blocks completely and doesn't react anymore. Reproducible: Always Steps to Reproduce: Mount a smb network path using mount.cifs, start dolphin and shutdown that server for the smb mount point. Actual Results: dolphin doesn't react anymore and blocks completely Expected Results: dolphin should simply ignore mount paths that are not available anymore and throw an error when trying to access that path.
Duplicate of 290855 and maybe 184062 ? Can anyone with the needed rights mark it as duplicate if appropriate? @Alexander Fieroch: Please check bug 184062 and see if hiding the "places" panel (press F9) before the disconnection helps.
Hm, I cannot reproduce the bug with current dolphin 2.0 (KDE 4.8.3). Instead of that the taskbar is hanging when a mounted network path is not available anymore but the system is still reacting and I can switch between applications using ALT+TAB. The bug in dolphin seems to be fixed...
I can reproduce this bug in dolphin with the version you said, see my comment #57 at bug 184062. Maybe you have disabled the "places" panel?
No, it's working for me but I don't have the mounted share folder in the places panel. When I was writing the bug report I didn't have the share folder in the places panel too. The whole system was hanging after unpluging network cable without unmounting. Even startmenu, shutdown or any application were hanging until timeout. That is fixed now. Your problem "only" occurs when the share folder is in the places panel and that is an other bug 184062 that has to be fixed.
I agree with you, this bug should be closed because it is not reproducible with your KDE 4.8.3 version and you were the only one reporting it.