GNOME Bugzilla – Bug 463892
crash in Open Folder: Logged in and I dont rem...
Last modified: 2007-08-25 15:56:25 UTC
Version: 2.18.1 What were you doing when the application crashed? Logged in and I dont remember if there was any problem on previous log-in. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 83755008 vsize: 83755008 resident: 24190976 share: 19369984 rss: 24190976 rss_rlim: 4294967295 CPU usage: start_time: 1186383362 rtime: 41 utime: 37 stime: 4 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 -1208994080 (LWP 25869)] (no debugging symbols found) 0x00731402 in __kernel_vsyscall ()
+ Trace 153119
Thread 1 (Thread -1208994080 (LWP 25869))
----------- .xsession-errors --------------------- (bug-buddy:25813): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:25813): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:25813): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension Initializing gnome-mount extension (nautilus:25848): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension Initializing gnome-mount extension (nautilus:25869): 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 452775 ***