GNOME Bugzilla – Bug 543001
crash in File Browser: Estaba accediendo a una ...
Last modified: 2008-07-14 23:56:43 UTC
Version: 2.20.0 What were you doing when the application crashed? Estaba accediendo a una carpeta de red comaprtida en un servidor windows 2003 Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 446160896 vsize: 446160896 resident: 31911936 share: 16785408 rss: 31911936 rss_rlim: 18446744073709551615 CPU usage: start_time: 1216077116 rtime: 114 utime: 106 stime: 8 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 0x2aae8bf4eb60 (LWP 4008)] (no debugging symbols found) 0x00002aae84adfedf in waitpid () from /lib/libpthread.so.0
+ Trace 202835
Thread 1 (Thread 0x2aae8bf4eb60 (LWP 4008))
----------- .xsession-errors (6 sec old) --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** 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: full-authentication!!! Advertencia del gestor de ventanas: Received a _NET_WM_MOVERESIZE message for 0x1400687 (Red de Win); these messages lack timestamps and therefore suck. --------------------------------------------------
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 ***