GNOME Bugzilla – Bug 497542
crash in Open Folder: Doing a search
Last modified: 2007-11-24 19:14:54 UTC
Version: 2.18.3 What were you doing when the application crashed? Doing a search Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 494280704 vsize: 494280704 resident: 46206976 share: 21192704 rss: 46206976 rss_rlim: 18446744073709551615 CPU usage: start_time: 1195259465 rtime: 1795 utime: 1304 stime: 491 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496352800 (LWP 2787)] [New Thread 1178638672 (LWP 4697)] (no debugging symbols found) 0x0000003b948c82e6 in poll () from /lib64/libc.so.6
+ Trace 178254
Thread 2 (Thread 1178638672 (LWP 4697))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib64/libgnomevfs-2.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib64/libselinux.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libgnome-window-settings.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libpanel-applet-2.so.0" is not at the expected address (wrong library or version mismatch?) warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff93dfd000 --------------------------------------------------
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 ***