I think that this is not right way to handle a bug that has been reported since three years and through even more distros releases.
I've just landed here for the first time since I'm using nautilus for sftp and was worried by this strange cpu activity even - and especially - after the download would end, fearing that my transfers could not have been cleanly closed. True that ie used in the past (more than a year ago) sftp and didn't recall this behaviour. I can reproduce at any tine: just open a remote sftp window and transfer (I've dragged the directory from my local directory window and dropped). Can see any other special setup that could influence, except that I 'm running a SSVNC session thus having two ssh sessions. Also I'm using key authentication, in case this matters. -- nautilus uses 100% cpu after closing a ssh session https://bugs.launchpad.net/bugs/27109 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
