GNOME Bugzilla – Bug 465786
crash in Open Folder: I was renamig a director...
Last modified: 2008-08-26 11:04:20 UTC
Version: 2.18.3 What were you doing when the application crashed? I was renamig a directory shared over SMB Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 84205568 vsize: 84205568 resident: 34369536 share: 14622720 rss: 34369536 rss_rlim: 4294967295 CPU usage: start_time: 1186867790 rtime: 5415 utime: 5320 stime: 95 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226139072 (LWP 13670)] [New Thread -1259684976 (LWP 13999)] (no debugging symbols found) 0xb7fdf7f2 in ?? () from /lib/ld-linux.so.2
+ Trace 154505
Thread 1 (Thread -1226139072 (LWP 13670))
----------- .xsession-errors (29632 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Messag ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 469818 has been marked as a duplicate of this bug. ***
*** Bug 470020 has been marked as a duplicate of this bug. ***
*** Bug 461055 has been marked as a duplicate of this bug. ***
*** Bug 477044 has been marked as a duplicate of this bug. ***
*** Bug 483882 has been marked as a duplicate of this bug. ***
*** Bug 486719 has been marked as a duplicate of this bug. ***
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 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! [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
*** Bug 478689 has been marked as a duplicate of this bug. ***
*** Bug 490809 has been marked as a duplicate of this bug. ***
*** Bug 499734 has been marked as a duplicate of this bug. ***
*** Bug 499746 has been marked as a duplicate of this bug. ***
*** Bug 500471 has been marked as a duplicate of this bug. ***
*** Bug 506805 has been marked as a duplicate of this bug. ***
*** Bug 509193 has been marked as a duplicate of this bug. ***
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? Preferably if you run Nautilus 2.20, 2.18 now is nearly a year old. 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
*** Bug 513334 has been marked as a duplicate of this bug. ***
*** Bug 514149 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!