GNOME Bugzilla – Bug 489293
crash in Home Folder: Programm geschlossen
Last modified: 2007-10-23 13:36:53 UTC
What were you doing when the application crashed? Programm geschlossen 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 125980672 vsize: 125980672 resident: 38735872 share: 24174592 rss: 38735872 rss_rlim: 4294967295 CPU usage: start_time: 1193085345 rtime: 13824 utime: 11358 stime: 2466 cutime:59 cstime: 27 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 -1209051424 (LWP 3393)] [New Thread -1303090288 (LWP 17738)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 172144
Thread 1 (Thread -1209051424 (LWP 3393))
----------- .xsession-errors --------------------- 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/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/libpanel-applet-2.so.0" 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 --------------------------------------------------
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 356672 ***