GNOME Bugzilla – Bug 551685
crash in File Browser: accediendo a una maquina...
Last modified: 2008-09-11 08:34:10 UTC
Version: 2.20.0 What were you doing when the application crashed? accediendo a una maquina en red con sistema operativo winwodws xp Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (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: 56991744 vsize: 56991744 resident: 27295744 share: 16265216 rss: 27295744 rss_rlim: 4294967295 CPU usage: start_time: 1221043908 rtime: 720 utime: 276 stime: 444 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6bec720 (LWP 2768)] (no debugging symbols found) 0xffffe402 in __kernel_vsyscall ()
+ Trace 206600
Thread 1 (Thread 0xb6bec720 (LWP 2768))
----------- .xsession-errors (22 sec old) --------------------- ** 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!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:2768): WARNING **: Hit unhandled case 31 (La operación ha sido cancelada) in fm_report_error_loading_directory --------------------------------------------------
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 ***