GNOME Bugzilla – Bug 471993
crash in File Browser:
Last modified: 2007-09-04 16:28:08 UTC
Version: 2.18.3 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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 85319680 vsize: 85319680 resident: 25112576 share: 20787200 rss: 25112576 rss_rlim: 4294967295 CPU usage: start_time: 1188419633 rtime: 53 utime: 37 stime: 16 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208625440 (LWP 4490)] (no debugging symbols found) 0x00293402 in __kernel_vsyscall ()
+ Trace 159192
Thread 1 (Thread -1208625440 (LWP 4490))
----------- .xsession-errors (29 sec old) --------------------- (bug-buddy:4357): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:4357): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension (nm-applet:3516): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch --------------------------------------------------
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 471979 ***