GNOME Bugzilla – Bug 552656
crash in File Browser:
Last modified: 2008-09-18 23:53:49 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango-Blue-Materia Memory status: size: 446472192 vsize: 446472192 resident: 34680832 share: 18739200 rss: 34680832 rss_rlim: 18446744073709551615 CPU usage: start_time: 1221666868 rtime: 191 utime: 174 stime: 17 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2ae500e79240 (LWP 7952)] [New Thread 0x40800950 (LWP 7986)] (no debugging symbols found) 0x00002ae4fa36fedf in waitpid () from /lib/libpthread.so.0
+ Trace 206894
Thread 1 (Thread 0x2ae500e79240 (LWP 7952))
----------- .xsession-errors --------------------- seahorse nautilus module initialized connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:7952): WARNING **: Hit unhandled case 31 (Anulowano operację) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:7952): WARNING **: Nie odnaleziono opisu typu MIME "x-directory/smb-share" (plik "Mp3"), napisz na listę gnome-vfs (w języku angielskim). --------------------------------------------------
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 ***