Well, scratch that. It's happening again right now, but for some reason my system is still usable. My problem now is that I can't run many programs or load files. I get an input/output error or an error saying that I'm attempting to access a read-only filesystem.
For instance: $ gnome-terminal Bonobo-Activation-Message: read-only filesystem locking '/tmp/orbit-$USERNAME/bonobo-activation-register.lock' $ ls / ls: cannot access /mnt: No such file or directory ls: cannot access /opt: No such file or directory ls: cannot access /srv: No such file or directory [...] $ sudo killall pidgin bash: /usr/bin/sudo: Input/output error Other commands like "man dd" or "xdvi somefile.dvi" just return without output. I suspect that the programs I can run right now are the ones that were already in memory when this all started. This time top shows ksoftirqd/0, pidgin, dd, klogd, and soffice.bin as the major cpu hogs, but I can't kill soffice.bin for instance (input/output error) or start xkill and try to shut it down that way (read-only filesystem error). I'm just speculating here, but maybe the indexer is the culprit. Would it have to make my whole filesystem read-only in order to scan it? I guess I'll have to start a new bug report for this one. -- Hardy Heron locks up https://bugs.launchpad.net/bugs/249123 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
