Yes I can confirm this in both Dapper and Edgy. Whenever the network connection between the two hosts is terminated, nautilus on the client (the one downloading) hits 100% CPU and remains there. It's quite a serious bug because the only way to bring back down the cpu is to do a 'killall nautilus'.
-- nautilus uses 100% cpu after closing a ssh session https://launchpad.net/bugs/27109 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
