GNOME Bugzilla – Bug 468819
crash in Open Folder: in firefox
Last modified: 2007-09-04 16:30:05 UTC
Version: 2.18.3 What were you doing when the application crashed? in firefox 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 82071552 vsize: 82071552 resident: 25100288 share: 18837504 rss: 25100288 rss_rlim: 4294967295 CPU usage: start_time: 1187697811 rtime: 65 utime: 59 stime: 6 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 -1208871200 (LWP 11287)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156808
Thread 1 (Thread -1208871200 (LWP 11287))
----------- .xsession-errors (8 sec old) --------------------- A handler is already registered for the path starting with path[0] = "org" Info: No sexy-python package found, don't worry it's optional. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Info: No sexy-python package found, don't worry it's optional. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. (nautilus:10872): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-open-terminal extension Initializing nautilus-image-converter extension Initializing nautilus-search-tool extension Initializing nautilus-flac-converter extension (nautilus:11287): 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 ***