GNOME Bugzilla – Bug 554053
crash in Open Folder:
Last modified: 2008-09-27 12:45:39 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26.5 #5 SMP Sat Sep 27 10:20:37 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 79482880 vsize: 79482880 resident: 12390400 share: 9564160 rss: 12390400 rss_rlim: 4294967295 CPU usage: start_time: 1222505621 rtime: 30 utime: 19 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ae4710 (LWP 4609)] (no debugging symbols found) 0xb72a53e1 in waitpid () from /lib/libpthread.so.0
+ Trace 207446
Thread 1 (Thread 0xb6ae4710 (LWP 4609))
----------- .xsession-errors (8 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/gab/.metacity/sessions/default0.ms: Failed to open file '/home/gab/.metacity/sessions/default0.ms': No such file or directory G_USER_DIRECTORY_DOWNLOAD is not set Initializing nautilus-open-terminal extension Initializing nautilus-share extension Initializing nautilus-image-converter extension Initializing gnome-mount extension beagled will run in the background. Use beagle-status to check progress of beagled. For log files check /home/gab/.beagle/Log/current-Beagle. seahorse nautilus module initialized --------------------------------------------------
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 355018 ***