GNOME Bugzilla – Bug 459528
crash in Home Folder: Suchen nach der Datei *....
Last modified: 2007-07-25 13:45:46 UTC
What were you doing when the application crashed? Suchen nach der Datei *.pnm 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-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 90390528 vsize: 90390528 resident: 32108544 share: 18538496 rss: 32108544 rss_rlim: 4294967295 CPU usage: start_time: 1185042452 rtime: 4483 utime: 3990 stime: 493 cutime:279 cstime: 91 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 -1208613152 (LWP 3009)] [New Thread -1259566192 (LWP 24301)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 149950
Thread 2 (Thread -1259566192 (LWP 24301))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/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/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/libpoppler-glib.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations 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 --------------------------------------------------
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 456445 ***