GNOME Bugzilla – Bug 494168
crash in Home Folder:
Last modified: 2007-11-08 01:27:28 UTC
What were you doing when the application crashed? 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Fedora Memory status: size: 73162752 vsize: 73162752 resident: 24711168 share: 20025344 rss: 24711168 rss_rlim: 4294967295 CPU usage: start_time: 1194358396 rtime: 39 utime: 36 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 -1208965408 (LWP 4407)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175734
Thread 1 (Thread -1208965408 (LWP 4407))
----------- .xsession-errors --------------------- (nautilus:4372): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension (nautilus:4385): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension (nautilus:4396): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * ) Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension (nautilus:4407): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --------------------------------------------------
*** This bug has been marked as a duplicate of 494164 ***