GNOME Bugzilla – Bug 540010
crash in Open Folder: Browsing samba share dir...
Last modified: 2008-06-24 22:50:23 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing samba share directory (Lenny server) 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: 86605824 vsize: 86605824 resident: 31899648 share: 16719872 rss: 31899648 rss_rlim: 4294967295 CPU usage: start_time: 1214328639 rtime: 2968 utime: 2718 stime: 250 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 0xb6ba8720 (LWP 3200)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201283
Thread 1 (Thread 0xb6ba8720 (LWP 3200))
----------- .xsession-errors (87 sec old) --------------------- (gnome-appearance-properties:3541): appearance-properties-WARNING **: Unknown Tag: comment (gnome-appearance-properties:3541): appearance-properties-WARNING **: Unknown Tag: comment (gnome-terminal:3374): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ** (nautilus:3200): WARNING **: No description found for mime type "x-directory/smb-share" (file is "ARCWIN"), 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 ***