GNOME Bugzilla – Bug 391147
crash in CD/DVD Creator: ctrl+l to /usr/src barel...
Last modified: 2007-04-21 17:26:15 UTC
What were you doing when the application crashed? ctrl+l to /usr/src barely openned it from the console as root Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 75808768 vsize: 0 resident: 75808768 share: 0 rss: 23179264 rss_rlim: 0 CPU usage: start_time: 1167524805 rtime: 0 utime: 120 stime: 0 cutime:114 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226983760 (LWP 9266)] (no debugging symbols found) 0xb7f58410 in __kernel_vsyscall ()
+ Trace 98157
Thread 1 (Thread -1226983760 (LWP 9266))
Thanks for taking the time to report this. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start Nautilus as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "Details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Ubuntu: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, libpango1.0-0-dbg, libgnomevfs2-0-dbg, and libgnomeui-0-dbg. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
*** Bug 408628 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 380774 ***
*** Bug 431983 has been marked as a duplicate of this bug. ***