GNOME Bugzilla – Bug 426149
crash in Home Folder:
Last modified: 2007-04-09 23:02:15 UTC
What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:00:19 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 474894336 vsize: 474894336 resident: 37814272 share: 20709376 rss: 37814272 rss_rlim: -1 CPU usage: start_time: 1175667061 rtime: 12447 utime: 1235 stime: 11212 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496347072 (LWP 3286)] 0x0000003aa120d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 124868
Thread 1 (Thread 46912496347072 (LWP 3286))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib64/libgssapi_krb5.so.2" is not at the expected address warning: .dynamic section for "/usr/lib64/libkrb5.so.3" is not at the expected address warning: .dynamic section for "/usr/lib64/libk5crypto.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libkrb5support.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: the debug information found in "/usr/lib/debug//usr/lib64/libnautilus-extension.so.1.1.0.debug" does not match "/usr/lib64/libnautilus-extension.so.1" (CRC mismatch). --------------------------------------------------
*** Bug 427504 has been marked as a duplicate of this bug. ***
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 349551 ***