Version: 4.7 (using KDE 4.7.0) OS: Linux I'm using kubuntu 11.04 64 bit, kde 4.7.0. When the NFS share is not more available ( nfs server power off, nfs service stopped ecc) all plasma desktop not more works... The right click over desktop not works, all plasma widget not works, but I can switch between windows (alt+tab). From system monitor I can see that plasma-desktop process's is on "disk waiting" status When the nfs share is available all return to works fine. best regards PS: this problem affects also kde 4.6.5 Reproducible: Always Steps to Reproduce: 1. mount a nfs share 2. from nfs server simply stop nfs service or shutdown the server Actual Results: after few seconds all plasma desktop freeze (as i already described on "details" tab). to unlock the whole desktop simply restart nfs service or boot up again the server. Expected Results: When the nfs service goes down for some reason, the plasma desktop should not crash, but it should continue to operate normally. Only the nfs mount point should not be more available.
Is the problem related to a specific widget/applet/plasmoid you use? In other words, if you start with a fresh new user account, can you check if there is any widget that causes the freeze?
Hi! Yes i just tried with new fresh user with only plasma-desktop and folder-view widget and when my nfs server goes down, the plasma-desktop freezes
Confirmed. Happens here as well.
Confirmed. Reproducible on: Arch Linux (kernel 3.1.0-4), Plasma 0.4, KDE SC 4.7.3 using Qt 4.7.4 The issue happens using the default settings (fresh user account).
Hi. This annoying problem is in KDE4 since early versions. I always had this problem as I use notebook. I believe that I also send a bug report, but it was never fixed. It would be good if someone can raise the priority on this and fix it fast. I work around the issue by manually unmounting the NFS exports, killing plasma-desktop, and starting plasma-desktop again.
Probably this is related to Bug 256291, Bug 158606 and Bug 228787. Can some of these maybe be marked as duplicate?
*** This bug has been marked as a duplicate of bug 256291 ***