GNOME Bugzilla – Bug 538708
crash in Open Folder: Just starting to browse ...
Last modified: 2008-06-17 07:49:33 UTC
Version: 2.20.0 What were you doing when the application crashed? Just starting to browse an smb share from another Debian/Lenny system 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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 98553856 vsize: 98553856 resident: 43651072 share: 16420864 rss: 43651072 rss_rlim: 4294967295 CPU usage: start_time: 1213670768 rtime: 2279 utime: 2152 stime: 127 cutime:249 cstime: 35 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 0xb6b7b720 (LWP 15652)] [New Thread 0xb4743b90 (LWP 20796)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200617
Thread 1 (Thread 0xb6b7b720 (LWP 15652))
----------- .xsession-errors (18 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) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (nautilus:15652): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Main%20Storage"), please tell the gnome-vfs mailing list. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! --------------------------------------------------
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 ***