Version: 3.5.8 release 33.2 (using KDE 3.5.8) Installed from: SuSE RPMs OS: Linux I guess is connected do a NFS Share that i have. When i make it offline, i forget to unmount here first. Then, when try to use the "start menu" from kde it doesn't work, or even konqueror opens and does nothing, having the symbol spining.
could this be a kio problem?
Does this still happen in KDE 4? It's a known fact that disconnected NFS mounts hang, but I wonder why the start menu or konqueror would care about some nfs-mounted user directory... Would be useful to attach gdb to the hanging process, or strace -p pid, to find out.
Created attachment 58603 [details] strace dolphin nfs freeze
This happens in KDE4 (4.6.0) dolphin too. Even worse - workmate's plasma-desktop was also in state D. He couldn't do anything on his desktop anymore. In our case it was a completely unimportant nfs read only mount. The user did nothing within that subtree. I reproduced it with dolphin and attached a strace. I killed dolphin while it was freezed so it hang at the last line. Obviously it repeats getting stats for all(!) mounts, which blocks for disconnected nfs. IMO the plasma-desktop freeze is even more more important to fix than dolphin. You can easily repeat it by yourself: - start NFS server - mount it somewhere - login KDE4 - stop NFS server
This bugs me too - plasma-desktop freezes entirely when there is (completely unrelated!) unreachable nfs mount on system. These processes show up as disk-waiting in top: plasma-desktop, ksysguardd (child of plasma), kded
*** This bug has been marked as a duplicate of bug 256291 ***
This is NOT a duplicate of bug 256291.