GNOME Bugzilla – Bug 486554
crash in Open Folder:
Last modified: 2007-10-15 12:20:10 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.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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 58400768 vsize: 58400768 resident: 23252992 share: 18640896 rss: 23252992 rss_rlim: 4294967295 CPU usage: start_time: 1192367350 rtime: 41 utime: 37 stime: 4 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 -1208310048 (LWP 8735)] 0x00110402 in __kernel_vsyscall ()
+ Trace 170132
Thread 1 (Thread -1208310048 (LWP 8735))
----------- .xsession-errors --------------------- (nautilus:8636): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Cannot access memory at address 0x0 Cannot access memory at address 0x0 (nautilus:8689): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Cannot access memory at address 0x0 (nautilus:8711): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:8724): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:8735): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Cannot access memory at address 0x0 Cannot access memory at address 0x0 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 472512 ***