GNOME Bugzilla – Bug 463370
crash in Open Folder:
Last modified: 2007-08-06 16:59:06 UTC
Version: 2.18.3 What were you doing when the application crashed? 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-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 77553664 vsize: 77553664 resident: 23298048 share: 18583552 rss: 23298048 rss_rlim: 4294967295 CPU usage: start_time: 1186214542 rtime: 72 utime: 61 stime: 11 cutime:0 cstime: 0 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 -1208097056 (LWP 7994)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 152732
Thread 1 (Thread -1208097056 (LWP 7994))
----------- .xsession-errors --------------------- warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstreamer-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstinterfaces-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libXtst.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations (nautilus:7994): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --------------------------------------------------
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 439593 ***