GNOME Bugzilla – Bug 395839
crash in CD/DVD Creator: It's odd, it seems to fa...
Last modified: 2007-02-04 22:17:24 UTC
What were you doing when the application crashed? It's odd, it seems to fail after trying to connect to a NT Domain share. What app's should I compile with debugging symbols for the backtrace? Distribution: Gentoo Base System version 1.12.8 Gnome Release: 2.16.2 2006-12-05 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 279527424 vsize: 279527424 resident: 42758144 share: 20561920 rss: 42758144 rss_rlim: -1 CPU usage: start_time: 1168422048 rtime: 882 utime: 658 stime: 224 cutime:12 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47592544901744 (LWP 10772)] [New Thread 1140881728 (LWP 28782)] 0x00002b4900510e46 in poll () from /lib/libc.so.6
+ Trace 101591
Thread 2 (Thread 1140881728 (LWP 28782))
Thanks for taking the time to report this bug. 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 debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 394317 ***