sorry, always forget to mention that, I'm running feisty. I've made 2 backtraces.
One where I started nautilus from the debugger, and one where I attached the debugger to an already open naulius. The naulius-dbg application seems to react differently then with dbg- extensions. Now nautilus is immediately non-responding (beryl also makes it appear in black-and-white). While without dbg it was still responding; only locking-up when I pressed the view-item from the menu. I think it also has to do something with beagle, which process also peaks when Nautilus is started with image-previews on. I could not find cairo libs with debug extension, don't know if this is also necessary (maybe I should install the dev version of this?) If you need more info please let me know. ** Attachment added: "nautilus traceback log, nautilus started from gdb" http://librarian.launchpad.net/7301241/gdb-nautilus.txt -- Nautilus cpu usage of 100%, locks up when pressing the view-menu https://bugs.launchpad.net/bugs/104558 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
