GNOME Bugzilla – Bug 462908
crash in Home Folder: perquisando o arquivo *i...
Last modified: 2007-08-02 20:36:00 UTC
What were you doing when the application crashed? perquisando o arquivo *itext* dentro do meu workspace Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 138190848 vsize: 138190848 resident: 27119616 share: 18935808 rss: 27119616 rss_rlim: 4294967295 CPU usage: start_time: 1185970832 rtime: 2477 utime: 1979 stime: 498 cutime:0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208191264 (LWP 2803)] [New Thread -1212429424 (LWP 24832)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 152402
Thread 2 (Thread -1212429424 (LWP 24832))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libmetacity-private.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstbase-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstreamer-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpoppler-glib.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 454799 ***