GNOME Bugzilla – Bug 533562
crash in Open Folder: open it
Last modified: 2008-05-17 13:45:09 UTC
Version: 2.20.0 What were you doing when the application crashed? open it 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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 95985664 vsize: 95985664 resident: 28446720 share: 15319040 rss: 28446720 rss_rlim: 4294967295 CPU usage: start_time: 1211012204 rtime: 14233 utime: 12223 stime: 2010 cutime:331 cstime: 29 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 0xb6be7720 (LWP 3778)] [New Thread 0xb55ffb90 (LWP 7678)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197954
Thread 1 (Thread 0xb6be7720 (LWP 3778))
----------- .xsession-errors (25 sec old) --------------------- Got Starorusskaya 0.977121 1 Got Starorusskaya 0.977121 1 Got Starorusskaya 0.981894 1 Got Starorusskaya 0.946047 1 Got Starorusskaya 0.979521 1 Got Starorussconnection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3778): WARNING **: No description found for mime type "x-directory/smb-share" (file is "A"), please tell the gnome-vfs mailing list. ** (nautilus:3778): WARNING **: Hit unhandled case 4 (Invalid parameters) in fm_report_error_loading_directory --------------------------------------------------
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 ***