GNOME Bugzilla – Bug 537959
crash in Open Folder:
Last modified: 2008-06-12 16:39:50 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 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: 73633792 vsize: 73633792 resident: 23085056 share: 14573568 rss: 23085056 rss_rlim: 4294967295 CPU usage: start_time: 1213220904 rtime: 139 utime: 124 stime: 15 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 0xb6e1f6b0 (LWP 3513)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200227
Thread 1 (Thread 0xb6e1f6b0 (LWP 3513))
----------- .xsession-errors (18 sec old) --------------------- SESSION_MANAGER=local/debian:/tmp/.ICE-unix/3455 Window manager warning: Failed to read saved session file /home/photo/.metacity/sessions/default0.ms: Failed to open file '/home/photo/.metacity/sessions/default0.ms': No such file or directory 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 Initializing gnome-mount extension ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 ***