I think I've seen this bug just happening here, while trying to reproduce bug 148781 and bug 150454. Therefor I've started a new gnome session and when exiting from there I've noticed that nautilus was using all available CPU cycles.
nautilus-debug-log.txt keeps growing, but only with the same "debug log dumped" line: ===== BEGIN MILESTONES ===== 0x8177888 2007/10/09 23:16:40.8978 (GLog): Can not calculate _NET_NUMBER_OF_DESKTOPS 0x8177888 2007/10/09 23:16:40.8979 (GLog): Can not calculate _NET_NUMBER_OF_DESKTOPS 0x8177888 2007/10/09 23:16:40.8979 (GLog): Can not get _NET_WORKAREA 0x8177888 2007/10/09 23:16:40.8980 (GLog): Can not determine workarea, guessing at layout 0x8177888 2007/10/09 23:23:20.6097 (USER): debug log dumped due to signal 11 0x8177888 2007/10/09 23:23:20.6246 (USER): debug log dumped due to signal 11 0x8177888 2007/10/09 23:23:20.6247 (USER): debug log dumped due to signal 11 0x8177888 2007/10/09 23:23:20.6248 (USER): debug log dumped due to signal 11 0x8177888 2007/10/09 23:23:20.6250 (USER): debug log dumped due to signal 11 [...] 0x8177888 2007/10/09 23:23:56.0296 (USER): debug log dumped due to signal 11 0x8177888 2007/10/09 23:23:56.0356 (USER): debug log dumped due to signal 11 ** Attachment added: "gdb backtrace of the nautilus process" http://launchpadlibrarian.net/9920515/nautilus-hangs-backtrace-150471.log ** Changed in: nautilus (Ubuntu) Status: Incomplete => Confirmed -- [Gutsy] high processor activity after logging out and then logging in again https://bugs.launchpad.net/bugs/150471 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
