GNOME Bugzilla – Bug 465054
crash in Open Folder: test
Last modified: 2007-08-10 14:11:31 UTC
Version: 2.18.3 What were you doing when the application crashed? test 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: Glossy P Icon Theme: OSX Memory status: size: 124923904 vsize: 124923904 resident: 37732352 share: 34177024 rss: 37732352 rss_rlim: 4294967295 CPU usage: start_time: 1186670302 rtime: 38 utime: 33 stime: 5 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 -1208973600 (LWP 3309)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 153973
Thread 1 (Thread -1208973600 (LWP 3309))
----------- .xsession-errors --------------------- (nautilus:3284): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension (nautilus:3298): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension (nautilus:3309): 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 ***