GNOME Bugzilla – Bug 536967
crash in File Browser: browse files while anoth...
Last modified: 2008-06-06 12:36:59 UTC
Version: 2.20.0 What were you doing when the application crashed? browse files while another is copying them in samba Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 559521792 vsize: 559521792 resident: 69046272 share: 20570112 rss: 69046272 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212741798 rtime: 2615 utime: 2331 stime: 284 cutime:2 cstime: 4 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2af46cca4240 (LWP 11065)] (no debugging symbols found) 0x00002af46619aedf in waitpid () from /lib/libpthread.so.0
+ Trace 199719
Thread 1 (Thread 0x2af46cca4240 (LWP 11065))
----------- .xsession-errors --------------------- class-mate : Navegador de archivos (_MainDock_) friend : Navegador de archivos (14683806) class-mate : Navegador de archivos (_MainDock_) friend : Navegador de archivos (14683806) class-mate : Navegador de archivos (_MainDock_) friend : Navegador de archivos (14683806) class-mate : Navegador de archivos (_MainDock_) friend : Navegador de archivos (14683806) class-mate : Navegador de archivos (_MainDock_) friend : Navegador de archivos (14683806) class-mate : Navegador de archivos (_MainDock_) friend : Navegador de archivos (14683806) class-mate : Navegador de archivos (_MainDock_) friend : Navegador de archivos (14683806) class-mate : Navegador de archivos (_MainDock_) --------------------------------------------------
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 ***