GNOME Bugzilla – Bug 539058
crash in Open Folder: opening network share
Last modified: 2008-06-19 07:49:08 UTC
Version: 2.20.0 What were you doing when the application crashed? opening network share Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu Mar 27 17:00:17 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 63524864 vsize: 63524864 resident: 27131904 share: 16289792 rss: 27131904 rss_rlim: 4294967295 CPU usage: start_time: 1213819988 rtime: 559 utime: 497 stime: 62 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c31720 (LWP 6158)] (no debugging symbols found) 0xb7645f91 in waitpid () from /lib/libpthread.so.0
+ Trace 200815
Thread 1 (Thread 0xb6c31720 (LWP 6158))
----------- .xsession-errors (13 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (gnome-settings-daemon:6129): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory (gnome-appearance-properties:6339): appearance-properties-WARNING **: Unknown Tag: comment (gnome-appearance-properties:6339): appearance-properties-WARNING **: Unknown Tag: comment ** (nautilus:6158): WARNING **: No description found for mime type "x-directory/smb-share" (file is "nils"), please tell the gnome-vfs mailing list. --------------------------------------------------
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 ***