GNOME Bugzilla – Bug 547578
crash in File Browser: przegladanie zasobow sie...
Last modified: 2008-08-13 14:02:05 UTC
Version: 2.20.0 What were you doing when the application crashed? przegladanie zasobow sieciowych, sieci LAN 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: 87203840 vsize: 87203840 resident: 26886144 share: 15007744 rss: 26886144 rss_rlim: 4294967295 CPU usage: start_time: 1218633794 rtime: 218 utime: 199 stime: 19 cutime:0 cstime: 0 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 0xb6aee930 (LWP 14918)] (no debugging symbols found) 0xb72953e1 in waitpid () from /lib/libpthread.so.0
+ Trace 205090
Thread 1 (Thread 0xb6aee930 (LWP 14918))
----------- .xsession-errors (24 sec old) --------------------- warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match seahorse nautilus module initialized Initializing gnome-mount extension --------------------------------------------------
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 ***