GNOME Bugzilla – Bug 544905
crash in Home Folder: Estava tentando conectar...
Last modified: 2008-07-27 09:53:49 UTC
What were you doing when the application crashed? Estava tentando conectar-me à minha pasta compartilhada no servidor de arquivos. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 63291392 vsize: 63291392 resident: 23691264 share: 14376960 rss: 23691264 rss_rlim: 4294967295 CPU usage: start_time: 1217107739 rtime: 376 utime: 344 stime: 32 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 0xb6ac5720 (LWP 2913)] (no debugging symbols found) 0xb7ef2424 in __kernel_vsyscall ()
+ Trace 203873
Thread 1 (Thread 0xb6ac5720 (LWP 2913))
----------- .xsession-errors --------------------- ** (nautilus:2913): WARNING **: Hit unhandled case 46 (Tempo limite atingido) in fm_report_error_loading_directory ** (nautilus:2913): WARNING **: Hit unhandled case 46 (Tempo limite atingido) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! warning: .dynamic section for "/usr/lib/libpcre.so.3" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***