GNOME Bugzilla – Bug 485153
crash in Open Folder: on file browser, in my h...
Last modified: 2007-10-10 23:11:58 UTC
Version: 2.18.3 What were you doing when the application crashed? on file browser, in my home folder, trying to open another folder inside my home Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-10-08 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.21-gentoo-r4 #1 SMP Wed Jul 18 20:17:14 WEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: LiNsta2 Icon Theme: glass-icons Memory status: size: 89243648 vsize: 89243648 resident: 35217408 share: 19468288 rss: 35217408 rss_rlim: 4294967295 CPU usage: start_time: 1191958294 rtime: 313 utime: 297 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1238645040 (LWP 31802)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 169085
Thread 1 (Thread -1238645040 (LWP 31802))
----------- .xsession-errors --------------------- aborting... Initializing gnome-mount extension ** (nautilus:31802): WARNING **: Cannot connect to system bus: org.freedesktop.DBus.Error.FileNotFound : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory ** (nautilus:31802): WARNING **: Could not initialize hal context (nautilus:31802): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (nautilus:31802): 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 ***