GNOME Bugzilla – Bug 476101
crash in Open Folder: Seeing
Last modified: 2007-09-13 10:09:39 UTC
Version: 2.18.1 What were you doing when the application crashed? Seeing 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.fc7PAE #1 SMP Fri Jul 27 18:01:30 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: 67403776 vsize: 67403776 resident: 24805376 share: 20566016 rss: 24805376 rss_rlim: 4294967295 CPU usage: start_time: 1189577740 rtime: 46 utime: 40 stime: 6 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 -1208441120 (LWP 4225)] (no debugging symbols found) 0x00110410 in __kernel_vsyscall ()
+ Trace 162260
Thread 1 (Thread -1208441120 (LWP 4225))
----------- .xsession-errors (8 sec old) --------------------- (nautilus:4124): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:4134): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:4160): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed CLIENT: Task: Task::done() CLIENT: Task: emitting finished (nautilus:4181): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:4204): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:4215): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:4225): 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 439977 ***