GNOME Bugzilla – Bug 485727
crash in Open Folder: Opening a folder in my h...
Last modified: 2007-10-13 00:17:41 UTC
Version: 2.18.3 What were you doing when the application crashed? Opening a folder in my home folder Distribution: Unknown Gnome Release: 2.18.3 2007-07-07 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.22-ARCH #1 SMP PREEMPT Wed Sep 26 20:57:40 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 57745408 vsize: 57745408 resident: 19558400 share: 13520896 rss: 19558400 rss_rlim: 4294967295 CPU usage: start_time: 1192111422 rtime: 131 utime: 125 stime: 6 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 -1227979072 (LWP 5959)] 0xb7f1b410 in __kernel_vsyscall ()
+ Trace 169496
Thread 1 (Thread -1227979072 (LWP 5959))
----------- .xsession-errors --------------------- aborting... Initializing gnome-mount extension ** (nautilus:5959): 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:5959): WARNING **: Could not initialize hal context (nautilus:5959): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (nautilus:5959): 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 ***