GNOME Bugzilla – Bug 537739
crash in Computer:
Last modified: 2008-06-11 11:13:54 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25.4-s3b-1.0 #1 SMP PREEMPT Sat May 17 18:25:47 CEST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Milk 2.0 Icon Theme: Neu Memory status: size: 466640896 vsize: 466640896 resident: 31965184 share: 18837504 rss: 31965184 rss_rlim: 18446744073709551615 CPU usage: start_time: 1213162830 rtime: 243 utime: 201 stime: 42 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 0x7f6fd030c7a0 (LWP 5310)] (no debugging symbols found) 0x00007f6fcb444edf in waitpid () from /lib/libpthread.so.0
+ Trace 200105
Thread 1 (Thread 0x7f6fd030c7a0 (LWP 5310))
----------- .xsession-errors --------------------- News & Blogs: FolderLoaded News & Blogs: FolderLoaded News & Blogs: FolderLoaded News & Blogs: FolderLoaded News & Blogs: FolderLoaded News & Blogs: FolderLoaded News & Blogs: FolderLoaded ** (nautilus:5310): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « g%24 »), veuillez avertir la liste de diffusion de gnome-vfs. connection_message_func(): Callback CALLBACK: fill-authentication!!! warning: .dynamic section for "/usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so" is not at the expected address (wrong library or version mismatch?) Error while mapping shared library sections: /usr/lib/liboobs-1.so.3: No such file or directory. --------------------------------------------------
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 ***