I agree that it is probably not nautilus directly. I suspect it is more probably due to the "udev" or "volumeid" change. But I could not revert these two and apparently reverting nautilus (and "libvolume-id0") was enough to stop it triggering the fault.
And no, when the crash occurs, I can't switch to VT. I haven't tried ssh but I tried a ping (at the time) and the machine didn't respond to it (when it usually does... So I would expect the ssh to fail too). As I said, when the machine crashes, there is nothing in the logs and the keyboard led (and the mouse) completly freeze, and that is usually the sign of a pretty bad lock up... Now, I haven't had a single crash since I reverted part of Friday's updates (as indicated earlier) and in fact I am reporting this bug from the machine that had the problem. I suspect I will be ok as long as I block automatic update or we somehow manage to identify the exact issue. -- Frequent total system freeze since Fri 29-Feb-08 security update https://bugs.launchpad.net/bugs/197900 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
