GNOME Bugzilla – Bug 537259
crash in Open Folder: I was browsing inside an...
Last modified: 2008-06-08 17:51:54 UTC
Version: 2.20.0 What were you doing when the application crashed? I was browsing inside an SMB share (changing to a subfolder) Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25.4 #1 SMP PREEMPT Sat May 24 21:19:30 EDT 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 470855680 vsize: 470855680 resident: 37761024 share: 20787200 rss: 37761024 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212936614 rtime: 3125 utime: 2598 stime: 527 cutime:127 cstime: 22 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 0x7f362718b7a0 (LWP 5774)] (no debugging symbols found) 0x00007f36222e1edf in waitpid () from /lib/libpthread.so.0
+ Trace 199866
Thread 1 (Thread 0x7f362718b7a0 (LWP 5774))
----------- .xsession-errors (37 sec old) --------------------- ** (nautilus:5774): WARNING **: Hit unhandled case 31 (Operation canceled) in fm_report_error_loading_directory ** (nautilus:5774): WARNING **: No description found for mime type "x-directory/smb-share" (file is "D%24"), 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!!! 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 ***