GNOME Bugzilla – Bug 491209
crash in Home Folder: Again opened a folder.
Last modified: 2007-11-08 00:13:29 UTC
What were you doing when the application crashed? Again opened a folder. Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-10-18 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.23-gentoo #3 SMP PREEMPT Sat Oct 13 00:32:05 EEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: OSX Memory status: size: 91381760 vsize: 91381760 resident: 32825344 share: 23126016 rss: 32825344 rss_rlim: 4294967295 CPU usage: start_time: 1193608666 rtime: 310 utime: 282 stime: 28 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1228642608 (LWP 29669)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 173538
Thread 1 (Thread -1228642608 (LWP 29669))
----------- .xsession-errors (8 sec old) --------------------- warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpangocairo-1.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libpangoft2-1.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpango-1.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgobject-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libglib-2.0.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 459221 ***