GNOME Bugzilla – Bug 518868
crash in Open Folder: Um...trying to switch be...
Last modified: 2008-02-26 20:25:06 UTC
Version: 2.18.3 What were you doing when the application crashed? Um...trying to switch between workspaces Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 60448768 vsize: 60448768 resident: 24174592 share: 19173376 rss: 24174592 rss_rlim: 4294967295 CPU usage: start_time: 946689599 rtime: 102 utime: 90 stime: 12 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 -1208809760 (LWP 2663)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190518
Thread 1 (Thread -1208809760 (LWP 2663))
----------- .xsession-errors --------------------- localuser:Robyn being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2365 (nautilus:2478): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:2633): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:2648): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (nautilus:2663): 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 we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 439977 ***