GNOME Bugzilla – Bug 448213
crash in File Browser: Closing the window
Last modified: 2007-06-23 11:22:20 UTC
Version: 2.18.1 What were you doing when the application crashed? Closing the window Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 407724032 vsize: 407724032 resident: 330665984 share: 52977664 rss: 330665984 rss_rlim: 4294967295 CPU usage: start_time: 1181987701 rtime: 315458 utime: 260743 stime: 54715 cutime:426 cstime: 238 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 -1208617248 (LWP 2614)] (no debugging symbols found) 0x00678402 in __kernel_vsyscall ()
+ Trace 141445
Thread 1 (Thread -1208617248 (LWP 2614))
----------- .xsession-errors (8 sec old) --------------------- warning: .dynamic section for "/usr/lib/libpoppler.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libstdc++.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libhal.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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 416114 ***