GNOME Bugzilla – Bug 461793
crash in Open Folder:
Last modified: 2007-08-06 14:21:40 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 98942976 vsize: 98942976 resident: 24875008 share: 20312064 rss: 24875008 rss_rlim: 4294967295 CPU usage: start_time: 1185801632 rtime: 29 utime: 26 stime: 3 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 -1208637728 (LWP 22684)] (no debugging symbols found) 0x007ee402 in __kernel_vsyscall ()
+ Trace 151589
Thread 1 (Thread -1208637728 (LWP 22684))
----------- .xsession-errors --------------------- Initializing nautilus-open-terminal extension (nautilus:22595): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-open-terminal extension (nautilus:22617): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-open-terminal extension (nautilus:22640): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-open-terminal extension (nautilus:22662): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-open-terminal extension (nautilus:22684): 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 ***