GNOME Bugzilla – Bug 553065
crash in Open Folder:
Last modified: 2008-09-24 09:56:25 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 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: 75005952 vsize: 75005952 resident: 23494656 share: 14319616 rss: 23494656 rss_rlim: 4294967295 CPU usage: start_time: 1221956040 rtime: 439 utime: 414 stime: 25 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 0xb6b63720 (LWP 2854)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 207026
Thread 1 (Thread 0xb6b63720 (LWP 2854))
----------- .xsession-errors (54 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/debian:/tmp/.ICE-unix/2769 ** Message: another SSH agent is running at: /tmp/ssh-PfxdYY2769/agent.2769 Could not start esd: Failed to execute child process "esd" (No such file or directory) ** (gnome-settings-daemon:2833): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Window manager warning: Failed to read saved session file /home/roger/.metacity/sessions/default0.ms: Failed to open file '/home/roger/.metacity/sessions/default0.ms': No such file or directory Initializing gnome-mount extension 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 522534 ***