On my Gutsyfied (from Feisty to Gutsy beta) Thinkpad T23 Nautilus goes to 100% CPU when the Gnome session is terminated. Best way to see this is to switch user from A to B, terminate user B's session and go back to A. The CPU is pegged with user B's dying Nautilus.
Possibly related: I quite often have to shoot down bonobo-activation- server to get Nautilus to start after having logged in and out once without a reboot. Terminating Nautilus (using nautilus -q) also leads to the dying nautilus hogging the CPU, all the while spewing dire '0x8177880 2007/09/30 23:26:54.2265 (USER): debug log dumped due to signal 11' warnings into nautilus-debug-log.txt at a rate of app. 7000 messages per second. After killing the morbid nautilus the CPU gets pegged by tracker which insists on indexing this logfile (easily remedied by deleting the offending log file but still...) -- 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 Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
