GNOME Bugzilla – Bug 530384
crash in Open Folder: I was opening a Windows ...
Last modified: 2008-04-28 18:06:15 UTC
Version: 2.20.0 What were you doing when the application crashed? I was opening a Windows share (the system default, C$) by clicking the triangle to the left of the folder icon. I'm not sure if a simple double-click causes the same problem. 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 Sat Apr 19 00:37:55 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: 76890112 vsize: 76890112 resident: 21970944 share: 14893056 rss: 21970944 rss_rlim: 4294967295 CPU usage: start_time: 1209397715 rtime: 183 utime: 171 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 0xb6b85720 (LWP 7153)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196346
Thread 1 (Thread 0xb6b85720 (LWP 7153))
----------- .xsession-errors --------------------- current dist not found in meta-release file connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3869): WARNING **: No description found for mime type "x-directory/smb-share" (file is "C%24"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:7153): WARNING **: No description found for mime type "x-directory/smb-share" (file is "C%24"), 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 ***