GNOME Bugzilla – Bug 533014
crash in File Browser:
Last modified: 2008-05-13 23:27:02 UTC
Version: 2.18.3 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.23.12-dream #1 SMP PREEMPT Fri Jan 18 02:13:57 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Go-Chrome Icon Theme: gnome Memory status: size: 83750912 vsize: 83750912 resident: 25681920 share: 15519744 rss: 25681920 rss_rlim: 4294967295 CPU usage: start_time: 1210720733 rtime: 278 utime: 254 stime: 24 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 0xb6c1a720 (LWP 4588)] (no debugging symbols found) 0xb765af91 in waitpid () from /lib/libpthread.so.0
+ Trace 197656
Thread 1 (Thread 0xb6c1a720 (LWP 4588))
----------- .xsession-errors --------------------- Warning: No symbols defined for <I7C> (keycode 252) Warning: No symbols defined for <I7D> (keycode 253) Warning: No symbols defined for <I7E> (keycode 254) Warning: No symbols defined for <I7F> (keycode 255) dpy: 0x8073f80 evt/error/major/minor: 111/176/1/0 dpy: 0x8073f80 evt/error/major/minor: 111/176/1/0 Launched application : 7413 connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:4588): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «Docs»); avvisare cortesemente la mailing list di gnome-vfs. --------------------------------------------------
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 ***