Comment 9 for bug 406154

Version: (using KDE 4.2.0)
Compiler: GCC 4.3.1
OS: Linux
Installed from: Gentoo Packages

How I manage to reproduce this on my machine: Use kickoff menu, have a NFS mount (in my case, mounted before KDE started), unplug the network cable and wait. Plasma hangs after a few seconds-minutes and comes back to life when I plug my network cable back. Also, adding the kickoff plugin when the network cable is unplugged results in a immediate crash.

I ran strace on plasma and the result when the hang appears is this:

lstat("/dev/md1", {st_mode=S_IFBLK|0640, st_rdev=makedev(9, 1), ...}) = 0
lstat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/dev/md2", {st_mode=S_IFBLK|0640, st_rdev=makedev(9, 2), ...}) = 0
lstat("/volatile", {st_mode=S_IFDIR|0755, st_size=56, ...}) = 0
lstat("/dev/md0", {st_mode=S_IFBLK|0640, st_rdev=makedev(9, 0), ...}) = 0
lstat("/boot", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
lstat("firebird:/home/ftp/pub", 0x7fffda66dec0) = -1 ENOENT (No such file or directory)
lstat("/home/ftp/pub", <unfinished ...>

So it is obviosly trying to lstat all devices *and* mountpoints. This leads to hangs, and I believe stating the nfs path is incorrect behaviour either way.

Of course, such hangs in apps are expected (and wanted) when nfs goes away, but having the whole plasma hang is quite an unpleasant side effect, and likely possible to fix. :)