GNOME Bugzilla – Bug 537636
crash in Home Folder: Tentando acessar compart...
Last modified: 2008-06-10 19:06:35 UTC
What were you doing when the application crashed? Tentando acessar compartilhamento samba. 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: 73949184 vsize: 73949184 resident: 20119552 share: 13025280 rss: 20119552 rss_rlim: 4294967295 CPU usage: start_time: 1213097457 rtime: 1261 utime: 1152 stime: 109 cutime:11 cstime: 2 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 0xb6b3e720 (LWP 3160)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200051
Thread 1 (Thread 0xb6b3e720 (LWP 3160))
----------- .xsession-errors (17 sec old) --------------------- Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a0789d (BrOffice.o) Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. 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: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 ***