Hey there,
From a while now, I've had this problem, hoping it would go away when the next dot release arrived...
I have 4 samba shares mounted on a server. When the connection is severed (if the router reboots, for example), the WHOLE plasma freezes until a the connection is established again.
Am I doing something wrong?

How did you mount the shares? Using smb://server/share/folder/ urls or by adding the appropriate lines to /etc/fstab?

This does not seem to be restricted to Samba shares.

I have the same effect - if I lose an NFS drive on one machine then the plasma-desktop freezes on a machine connected to it.

This happens on a machine with Lucid and a machine with Natty - same cause - loss of a network drive, and happens in both directions.

Dropping into a terminal and killing and restarting plasma-desktop makes no difference.

I can only get plasma-desktop back if the network drive reappears.

Any thoughts here, please?

John

This is standard UNIX behaviour. If you mount a file system into the system directly, so that it is present in the output of "mount" and the connection fails - then all applications interacting with files on that area of the file system will hang. The applications will remain hung indefinitely, waiting for i/o and cannot be killed.

There is nothing that can be done about this unfortunately, other than using the proper KIO methods to access these drives, through the nfs:// and smb:// protocols, rather than mounting them into the file system.