GNOME Bugzilla – Bug 478031
crash in Open Folder:
Last modified: 2007-09-18 19:31:41 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.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Raleigh Icon Theme: gnome Memory status: size: 78118912 vsize: 78118912 resident: 18038784 share: 13602816 rss: 18038784 rss_rlim: 4294967295 CPU usage: start_time: 1190121504 rtime: 186 utime: 144 stime: 42 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209030944 (LWP 14667)] 0x0012d402 in __kernel_vsyscall ()
+ Trace 163746
Thread 1 (Thread -1209030944 (LWP 14667))
----------- .xsession-errors --------------------- (gnome-terminal:14466): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (bug-buddy:14593): GLib-GObject-WARNING **: invalid uninstantiatable type `gdouble' in cast to `GObject' (bug-buddy:14593): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:14593): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:14593): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers)) aborting... Cannot access memory at address 0x394b Cannot access memory at address 0x394b --------------------------------------------------
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 459221 ***