GNOME Bugzilla – Bug 536337
crash in Open Folder: opening a file
Last modified: 2008-06-02 22:45:26 UTC
Version: 2.20.0 What were you doing when the application crashed? opening a file Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 82726912 vsize: 82726912 resident: 28573696 share: 16084992 rss: 28573696 rss_rlim: 4294967295 CPU usage: start_time: 1212428958 rtime: 1640 utime: 1376 stime: 264 cutime:0 cstime: 3 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 0xb6c23720 (LWP 2791)] [New Thread 0xb4fe0b90 (LWP 2857)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199442
Thread 1 (Thread 0xb6c23720 (LWP 2791))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/hprose:/tmp/.ICE-unix/2708 ** Message: another SSH agent is running at: /tmp/ssh-jwEjzw2708/agent.2708 ** (gnome-settings-daemon:2769): 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/jenny1/.metacity/sessions/default0.ms: Failed to open file '/home/jenny1/.metacity/sessions/default0.ms': No such file or directory Initializing gnome-mount extension seahorse nautilus module initialized (nautilus:2791): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 ***