GNOME Bugzilla – Bug 401574
crash in CD/DVD Creator: deleting a junk app
Last modified: 2007-07-30 03:02:15 UTC
What were you doing when the application crashed? deleting a junk app Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 97402880 vsize: 0 resident: 97402880 share: 0 rss: 14741504 rss_rlim: 0 CPU usage: start_time: 1169958355 rtime: 0 utime: 815 stime: 0 cutime:738 cstime: 0 timeout: 77 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 -1226910032 (LWP 4483)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 105865
Thread 1 (Thread -1226910032 (LWP 4483))
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 402862 has been marked as a duplicate of this bug. ***
*** Bug 410257 has been marked as a duplicate of this bug. ***
Dear reporters, could you please help fixing this by installing some debugging packages [1], start the application 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 for helping to get this fixed! [1] Please install debug packages for glib2 and gtk2. Ubuntu 6.10: libglib2.0-0-dbg, libgtk2.0-0-dbg Fedora Core 6 or OpenSuSE 10.2: glib2-debuginfo, gtk2-debuginfo More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 416982 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!