Note: my problem appears to be directly related to File Operations. What follows is a copy of related comment I just added to Bug 698109:
I've narrowed this down to the nub. The specific bug as can thus far be certain: Nautilus freezes when separate File Operation interrupted with Error caused by over-long filename. To recap: I have Nautilus running in Ubuntu Workspace 1. I have a large File Operation running in Workspace 4. When the File Operation in Workspace 4 is interrupted with an error such as "File name too long", my instance of Nautilus in Workspace 1 freezes. When I clear the File Operation error in Workspace 4, Nautilus becomes operative again in Workspace 1. Perhaps it is normal behaviour for a File Operation error message to prevent other actions. But I can use other programs while the FO Error is waiting for my attention in Workspace 4. I can, for example, use Firefox and Update Manager or run a terminal. I just can't use the Nautilus window I already had open. Note that I can open a new Nautilus window while the FO Error is waiting my attention. But once the new Nautilus Window has opened I am unable to use it. Neither can I close it. If, however, I tell the File Operation Error dialogue in Workspace 4 to [Skip], Nautilus starts working again in Workspace 1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/428564 Title: nautilus crashed while copying a set of large files -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
