GNOME Bugzilla – Bug 534356
crash in File Browser: I'm trying to browse a s...
Last modified: 2008-05-22 17:48:42 UTC
Version: 2.20.0 What were you doing when the application crashed? I'm trying to browse a shared folder in My Windows2000 file server 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 Sat Apr 19 00:37:55 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: 103845888 vsize: 103845888 resident: 31645696 share: 17309696 rss: 31645696 rss_rlim: 4294967295 CPU usage: start_time: 1211446818 rtime: 1124 utime: 1024 stime: 100 cutime:14 cstime: 3 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 0xb6b90720 (LWP 3376)] [New Thread 0xb56e2b90 (LWP 5416)] [New Thread 0xb4cffb90 (LWP 4880)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198383
Thread 1 (Thread 0xb6b90720 (LWP 3376))
----------- .xsession-errors (11 sec old) --------------------- Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e1e670 (Esporta) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e1e670 (Esporta) Avviso del window manager: 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: full-authentication!!! connection_message_func(): Callback CALLBACK: save-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 ***