Bug 185552 - plasma freeze when nfs server goes down
Summary: plasma freeze when nfs server goes down
Status: RESOLVED DUPLICATE of bug 184062
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
Depends on:
Reported: 2009-02-25 18:59 UTC by francis
Modified: 2009-02-27 10:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Note You need to log in before you can comment on or make changes to this bug.
Description francis 2009-02-25 18:59:20 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

my main computer (with the problem) runs openSUSE 11.1 (x86_64) with 4.2.00 (KDE 4.2.0) "release 83.1". Another older pc (opensuse 10.2) runs as fileserver.
Whenever I shut the server down, plasma-widgets on the desktop freeze (not responding when clicking them); the same goes for the widgets in my panel, except for the system-tray (!!).
When I open Syst monitor (ksysguard) I find: "plasma - schijf inactief" and also below: "ksysguard - schijf inactief" meaning "disk inactive"
In /var/log/messages I read: "kernel: nfs: server () not responding, still trying"
But no crash-report or whatever.
When I try to restart the X-server: CTRL+ALT+backspace (2x) I get back to the login screen. But after login I get a black screen. 
The only thing I can do then is restart the pc.
I have no idea why plasma freezes when the nfs server goes down.
the problem is reproducible at 100%. It always happens when I shut the server down.
Comment 1 francis 2009-02-25 21:56:11 UTC
extra info: in systemmonitor the table of processes is filling with lots of "kio_sysinfo" all with CPU% = "schijf inactief" (meaning disk inactive).
It is also impossible to save any file. I wanted to attach a snapshot of this but couldn't save the file.
Available memory is dropping fast with every new "kio_sysinfo" line
Comment 2 francis 2009-02-27 10:02:33 UTC

*** This bug has been marked as a duplicate of bug 184062 ***