GNOME Bugzilla – Bug 536075
crash in File Browser: I'm trying of opening a ...
Last modified: 2008-06-02 09:20:10 UTC
Version: 2.20.0 What were you doing when the application crashed? I'm trying of opening a folder in a remote pc Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.21.5-25062007 #1 SMP PREEMPT Mon Jun 25 09:48:04 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Amaranth Icon Theme: default.kde Memory status: size: 113324032 vsize: 113324032 resident: 41103360 share: 20516864 rss: 41103360 rss_rlim: 4294967295 CPU usage: start_time: 1212318073 rtime: 13005 utime: 11723 stime: 1282 cutime:23 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1229953248 (LWP 6420)] 0xb7f81410 in __kernel_vsyscall ()
+ Trace 199334
Thread 1 (Thread -1229953248 (LWP 6420))
----------- .xsession-errors (14712 sec old) --------------------- (nero:10964): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:10964): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:10964): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:10964): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:10964): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:10964): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:10964): GLib-CRITICAL **: ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522534 ***