GNOME Bugzilla – Bug 486001
crash in Open Folder: opening a directory
Last modified: 2007-10-13 00:16:43 UTC
Version: 2.18.3 What were you doing when the application crashed? opening a directory Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-09-21 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-kamikaze7 #1 SMP PREEMPT Mon Aug 27 01:12:25 HST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Water Vapor Icon Theme: glass-icons Memory status: size: 309436416 vsize: 309436416 resident: 39710720 share: 21397504 rss: 39710720 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192190241 rtime: 81 utime: 76 stime: 5 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 47570040571280 (LWP 7332)] [New Thread 1090541888 (LWP 7349)] [New Thread 1082149184 (LWP 7348)] [New Thread 1132505408 (LWP 7347)] [New Thread 1149290816 (LWP 7346)] [New Thread 1157683520 (LWP 7345)] [New Thread 1140898112 (LWP 7344)] 0x00002b43c125d53e in waitpid () from /lib/libpthread.so.0
+ Trace 169714
Thread 1 (Thread 47570040571280 (LWP 7332))
----------- .xsession-errors --------------------- aborting... Initializing gnome-mount extension ** (nautilus:7332): WARNING **: Failed to initialize libhal context: (null) : (null) ** (nautilus:7332): WARNING **: Could not initialize hal context (nautilus:7332): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (nautilus:7332): GLib-GObject-CRITICAL **: g_object_weak_ref: assertion `G_IS_OBJECT (object)' failed Shutting down gnome-mount extension ** 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... --------------------------------------------------
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 ***