GNOME Bugzilla – Bug 492803
crash in Open Folder:
Last modified: 2007-11-03 01:43:39 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.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: 105689088 vsize: 105689088 resident: 36261888 share: 22425600 rss: 36261888 rss_rlim: 4294967295 CPU usage: start_time: 1194030627 rtime: 679 utime: 550 stime: 129 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 -1208281376 (LWP 24911)] [New Thread -1221239920 (LWP 24945)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174679
Thread 2 (Thread -1221239920 (LWP 24945))
----------- .xsession-errors (11 sec old) --------------------- (bug-buddy:24903): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:24903): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:24903): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension --- Hash table keys for warning below: --> file:///home/daniel (nautilus:24930): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:24911): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x2271)! --------------------------------------------------
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 ***