GNOME Bugzilla – Bug 546460
crash in File Browser: abriendo un recurso comp...
Last modified: 2008-08-05 18:57:06 UTC
Version: 2.20.0 What were you doing when the application crashed? abriendo un recurso compartido de windows - opening a shared directory on a winXP host Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-amd64 #1 SMP Sun Feb 10 22:28:37 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 91086848 vsize: 91086848 resident: 30580736 share: 15597568 rss: 30580736 rss_rlim: 18446744073709551615 CPU usage: start_time: 1217961507 rtime: 437 utime: 383 stime: 54 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 0xf6b91940 (LWP 31763)] (no debugging symbols found) 0xf7328f91 in waitpid () from /lib/libpthread.so.0
+ Trace 204658
Thread 1 (Thread 0xf6b91940 (LWP 31763))
----------- .xsession-errors --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4 Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:31763): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «compartida»), avise a la lista de correo de gnome-vfs. warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4 --------------------------------------------------
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 ***