GNOME Bugzilla – Bug 539410
crash in Open Folder: Preparing to move files ...
Last modified: 2008-06-21 10:01:27 UTC
Version: 2.20.0 What were you doing when the application crashed? Preparing to move files across a lan? Distribution: Unknown Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 477908992 vsize: 477908992 resident: 36061184 share: 17457152 rss: 36061184 rss_rlim: 18446744073709551615 CPU usage: start_time: 1214019129 rtime: 811 utime: 725 stime: 86 cutime:4 cstime: 2 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 0x2ad88cab4220 (LWP 4406)] [New Thread 0x40821950 (LWP 4647)] (no debugging symbols found) 0x00002ad885b8bedf in waitpid () from /lib/libpthread.so.0
+ Trace 200989
Thread 1 (Thread 0x2ad88cab4220 (LWP 4406))
----------- .xsession-errors (9 sec old) --------------------- xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Window manager warning: Failed to read saved session file /home/byron/.metacity/sessions/default0.ms: Failed to open file '/home/byron/.metacity/sessions/default0.ms': No such file or directory Initializing gnome-mount extension seahorse nautilus module initialized closing gnome-mount 0.7 closing gnome-mount 0.7 connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 522534 ***