GNOME Bugzilla – Bug 580153
crash in Open Folder: I was trying to open pho...
Last modified: 2009-04-24 18:08:21 UTC
Version: 2.20.0 What were you doing when the application crashed? I was trying to open photo folder on the server . Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Fri Mar 13 18:08:45 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 73916416 vsize: 73916416 resident: 30912512 share: 15761408 rss: 30912512 rss_rlim: 4294967295 CPU usage: start_time: 1240595108 rtime: 214 utime: 202 stime: 12 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 0xb6b00720 (LWP 7587)] (no debugging symbols found) 0xb7f29424 in __kernel_vsyscall ()
+ Trace 214768
Thread 1 (Thread 0xb6b00720 (LWP 7587))
----------- .xsession-errors --------------------- CALLBACK: save-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:7419): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Photos"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:7451): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Music"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:7587): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Photos"), 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 ***