GNOME Bugzilla – Bug 544930
crash in File Browser: intentaba explorar una r...
Last modified: 2008-07-27 09:52:33 UTC
Version: 2.20.0 What were you doing when the application crashed? intentaba explorar una red de windows :S Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 82903040 vsize: 82903040 resident: 31830016 share: 15839232 rss: 31830016 rss_rlim: 4294967295 CPU usage: start_time: 1217134325 rtime: 290 utime: 261 stime: 29 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b7a720 (LWP 6188)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 203888
Thread 1 (Thread 0xb6b7a720 (LWP 6188))
----------- .xsession-errors --------------------- (firefox-bin:5240): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5240): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5240): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5240): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:6188): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Documentos%20Compartidos»), avise a la lista de correo de 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 ***