GNOME Bugzilla – Bug 465579
crash in Open Folder: restart
Last modified: 2007-10-15 12:42:43 UTC
Version: 2.18.3 What were you doing when the application crashed? restart 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 86855680 vsize: 86855680 resident: 22925312 share: 18321408 rss: 22925312 rss_rlim: 4294967295 CPU usage: start_time: 1186801304 rtime: 36 utime: 33 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 -1209047328 (LWP 3251)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154351
Thread 1 (Thread -1209047328 (LWP 3251))
----------- .xsession-errors --------------------- (nautilus:3157): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:3178): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:3202): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:3223): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --- Hash table keys for warning below: --> file:///home/rohizam (nautilus:3246): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3251): 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 ***
*** Bug 483462 has been marked as a duplicate of this bug. ***
*** Bug 483464 has been marked as a duplicate of this bug. ***
*** Bug 486580 has been marked as a duplicate of this bug. ***