GNOME Bugzilla – Bug 533015
crash in File Browser:
Last modified: 2008-05-13 23:27:09 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: 86847488 vsize: 86847488 resident: 29085696 share: 15515648 rss: 29085696 rss_rlim: 4294967295 CPU usage: start_time: 1210721065 rtime: 188 utime: 175 stime: 13 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 0xb6b6c720 (LWP 8329)] (no debugging symbols found) 0xb75acf91 in waitpid () from /lib/libpthread.so.0
+ Trace 197657
Thread 1 (Thread 0xb6b6c720 (LWP 8329))
----------- .xsession-errors --------------------- 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. Initializing nautilus-open-terminal extension Initializing gnome-mount extension Launched application : 8426 Launched application : 8488 ** (nautilus:8329): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «DivX»); 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 ***