I apologize because I am a newb. However, the backtrace seemed to reveal nothing since nautilus never actually crashed for me. Here is what I did:
1. started nautilus using gdb as directed in the wiki above. 2. I browsed to my /usr/lib folder 3. after about 10 seconds my nautilus went gray (I believe to show it was not responding to user events) 4. after about 40 or 50 seconds my nautilus process had gone from using roughly 50 MB to roughly 170MB and it was still not responding. 5. I think forced nautilus to quit and finished the instructions to do a backtrace (posted below). GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... (gdb) handle SIG33 pass nostop noprint Signal Stop Print Pass to program Description SIG33 No No Yes Real-time event 33 (gdb) set pagination 0 (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] [New Thread 0x7f106f6127a0 (LWP 25638)] [New Thread 0x41718950 (LWP 25641)] [New Thread 0x424a1950 (LWP 25643)] Program exited normally. (gdb) backtrace full No stack. (gdb) info registers The program has no registers now. (gdb) backtrace full No stack. (gdb) backtrace full No stack. (gdb) info registers The program has no registers now. (gdb) thread apply all bakc[K[Kcktrace No registers. (gdb) quit What else can I do to help? James James -- crashes listing directory of ntfs-3g fakeraid as user https://bugs.launchpad.net/bugs/250192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
