GNOME Bugzilla – Bug 492829
crash in Open Folder: File Browser
Last modified: 2007-11-03 01:43:50 UTC
Version: 2.18.3 What were you doing when the application crashed? File Browser 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106303488 vsize: 106303488 resident: 35876864 share: 22421504 rss: 35876864 rss_rlim: 4294967295 CPU usage: start_time: 1194030985 rtime: 717 utime: 581 stime: 136 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 -1208338720 (LWP 25013)] [New Thread -1210803312 (LWP 25316)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174697
Thread 2 (Thread -1210803312 (LWP 25316))
----------- .xsession-errors (7 sec old) --------------------- (bug-buddy:25006): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:25006): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:25006): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2a0000f specified for 0x2a0000d (). --- Hash table keys for warning below: --> file:///home/daniel (nautilus:25304): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:25013): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 454799 ***